Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.datemas.de!rt.uk.eu.org!aioe.org!.POSTED!not-for-mail From: Helpful Harry Newsgroups: comp.databases.filemaker Subject: Re: Strange file opening problem Date: Tue, 03 Sep 2013 13:21:41 +1200 Organization: Aioe.org NNTP Server Lines: 36 Message-ID: <030920131321417171%HelpfulHarry@BusyWorking.com> References: NNTP-Posting-Host: YkMrwR3FpI0Lm2YmR6NRkw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Thoth/1.5.4 (Carbon/OS X) X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.databases.filemaker:1354 In article , John G wrote: > After serious thinking Nigel James wrote : > > Hi, I have a baffling little file-opening problem I'd appreciate any wisdom > > for. > > > > I've been using Filemaker since v3, now using v12 on a Mac running OS X > > 10.8.4 Mountain Lion. I have always started Filemaker by opening whichever > > database I want to work in (rather than starting Filemaker first, then > > opening the file I want). > > > > Suddenly and for no reason I can fathom, whichever database I want to open > > Filemaker with, it fails to open. Filemaker starts and immediately presents > > an "Open new or existing file" to choose a database or other file. > > > > Very strange. Does anyone have experience of this? > > > > Grateful for any wisdom. Thanks in advance. > > If this was WinDoze I would say the file association has been changed > and it easy to change back from the control Panel and other places. > But I have no idea how Mac handles file associations. That was my first thought too, but FileMaker does open (so the system does know it is a FileMaker document), it just doesn't the actual database file that was double-clicked. BUT it might still be worth double-checking by clicking on a file that doesn't open properly and looking in the Get Info window to see which application it is using as the default to open it. It might also be worth running the Repair Permissions options in the Disk Utility application (in the Applications -> Utilities folder). Helpful Harry :o)