How do I open a file without performing the File Options? I need to change the script which I stupidly entered.

I set up a script to close the file which it does perfectly, so that I can

Hi Florida,

"Is there a file option script to store the file in the dock instead of closing it?"

There is a difference between closing a File and exiting the FM application. On Windows, you can't Minimize the FM application itself via script (which kinda makes sense). But with script-step called Adjust Window[] you can select Minimize (which minimizes the window within the FM application). So if it's the only open window for that file, the 'file' will minimize. You can also Hide the window/file (so Users can't maximize it) but be careful here. If it's the only window open and you Hide it, it'll close the file (at least on Windows it does). So does Close Window[]. Mac users may have a way of docking the whole App via Apple Script or something. We Windows users must click the App 'minimize' to place it on our, ummmm, docks (task bars?).

And welcome to FM Forums, by the way!

Update: I realize I shouldn't have answered because of the differences between OS' so please Mac people, straighten this out. I'll bet Macs can do it!!! What would happen if it was cross-platform solution tho? Again, unknown. Sorry.

LaRetta

"How do I open a file without performing the File Options?"

Get any other FMP file and define a relationship to the database you want to open.

LaRetta you did good.

But it does solve the problem of the opening script closing the file before it can be worked on. I think thaat the only way to stop the opening script is with the script debugger which is part of Developer and not available in FMP7.

If you will post a copy of your database, I will be glad to remove that script step and send it back to you.

Try holding down command-period after logging in. This should cancel the opening script (unless you have "Allow user abort" turned off.)

Hi Ralph

I didn't realize she had written the close into her startup. She can try hitting [esc] repeatedly also if she hasn't included an Allow User Abort[Off]. She'll have to be very fast!!. And as Vaughan indicates, if she leaves it closed and creates a relationship from another file to it (if allowed) and places that file's field on her other file opening layout, it will open her 'bad' file (without running it's startup script from File Options).

Oh. I sympathize. I've never done this specific thing but I've caught myself in never-ending loops (with Allow User Abort [Off] more than once.

LaRetta

Mike!

Is there a similar key combination for Windows? To the command-period? Just in case I ever, errr, do something like this also?

First, Macs don't mess with your applications. Closing windows and closing the application are entirely independent. Which is much more convenient (IMHO). Perhaps Bill Gates assumed that people are not smart enough to know whether an application is open or not (which would have mattered back in the old days, when RAM was expensive). Of course, Steve Jobs does the opposite; he assumes you're not smart enough to open a window when you launch an application (a few Apple applications open a document automatically when you launch; which is usually OK, but can be annoying; Script Editor is a good example). A curse on both your houses -]

As to Frank's problem, it's very difficult to bypass the opening script in FileMaker 7. The opening script runs as soon as a window of the file becomes visible. It's a feature. But it doesn't seem that way when you screw up and can't open your file.

If you have any script in the file that ends with Halt Script, you can call that from another file. Otherwise if you have a script that has a Loop or other operation that goes on for a while, you could call that; so you can try and cancel it.

It's a good idea to include a clause in the opening script so that it doesn't continue if certain command keys are down. I use modifier keys <> (does not equal) 12, Control-Opt or Alt, 'cause it's much the same on both platforms. Also 'cause the Option key triggers the password dialog.

" it's very difficult to bypass the opening script in FileMaker 7"

Let(

Offending file = DAWG);

Then this is different than prior versions? Because I know that if DAWG is only opened in response to viewing a layout in another file which contains a field from DAWG, DAWG's opening script doesn't run at all (one of it's drawbacks; at least in prior versions). I assumed that remained the same in 7? You don't need to display the DAWG's window at all do you - if you just create a file reference to it and display DAWG's field on a related layout, right? I think I would try this process for sure if other methods fail before giving up.

)