Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.filemaker > #1346 > unrolled thread
| Started by | Nigel James <crewedcharter@gmail.com> |
|---|---|
| First post | 2013-09-02 03:04 -0700 |
| Last post | 2013-09-03 13:21 +1200 |
| Articles | 4 — 3 participants |
Back to article view | Back to comp.databases.filemaker
Strange file opening problem Nigel James <crewedcharter@gmail.com> - 2013-09-02 03:04 -0700
Re: Strange file opening problem Helpful Harry <HelpfulHarry@BusyWorking.com> - 2013-09-03 09:13 +1200
Re: Strange file opening problem John G <greentest@ozemail.com.au> - 2013-09-03 09:31 +1000
Re: Strange file opening problem Helpful Harry <HelpfulHarry@BusyWorking.com> - 2013-09-03 13:21 +1200
| From | Nigel James <crewedcharter@gmail.com> |
|---|---|
| Date | 2013-09-02 03:04 -0700 |
| Subject | Strange file opening problem |
| Message-ID | <feb6f596-5d85-440d-95cb-b50f38dcd37b@googlegroups.com> |
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.
[toc] | [next] | [standalone]
| From | Helpful Harry <HelpfulHarry@BusyWorking.com> |
|---|---|
| Date | 2013-09-03 09:13 +1200 |
| Message-ID | <030920130913194502%HelpfulHarry@BusyWorking.com> |
| In reply to | #1346 |
In article <feb6f596-5d85-440d-95cb-b50f38dcd37b@googlegroups.com>, Nigel James <crewedcharter@gmail.com> 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. I have no idea whay that would happen, but a few things to try ... Does the database file open properly if you then use the application's open command? Are they "updated" database fiels from older versions of FileMaker or does it happen with newly created FileMaker 12 files as well? Is there something in a startup script for the database file that could be making it close again or show the Open dialog window? I don't know if it's related, but FileMaker 3 and 4 have a similar behaviour on my Mac (Mac OS X 10.1 and now 10.2. Since they're both applications that require the Classic environment to load, I have noticed that if I double-click a database file and then go back to doing something else while Classic loads, then the FileMaker application opens, but then it stops and bounces the Dock icon and if I'm not "quick enough" going back to it, it doesn't actually open the file (no Open dialog window either). Double-clicking the file again does open it. Helpful Harry :o)
[toc] | [prev] | [next] | [standalone]
| From | John G <greentest@ozemail.com.au> |
|---|---|
| Date | 2013-09-03 09:31 +1000 |
| Message-ID | <NsudnU2SpudygrjPnZ2dnUVZ_sKdnZ2d@westnet.com.au> |
| In reply to | #1346 |
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. -- John G
[toc] | [prev] | [next] | [standalone]
| From | Helpful Harry <HelpfulHarry@BusyWorking.com> |
|---|---|
| Date | 2013-09-03 13:21 +1200 |
| Message-ID | <030920131321417171%HelpfulHarry@BusyWorking.com> |
| In reply to | #1353 |
In article <NsudnU2SpudygrjPnZ2dnUVZ_sKdnZ2d@westnet.com.au>, John G <greentest@ozemail.com.au> 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)
[toc] | [prev] | [standalone]
Back to top | Article view | comp.databases.filemaker
csiph-web