Whoops!

I put:

Close Window [Current Window]

as the first line of my startup script. Now, the file closes the moment
I open it. How do I recover? I tried the Escape key and cntl-f8. No
luck.

I am using FM7.0v3 on WindowsXP

Thanks,
Tony

Tony,

If you have any script in "Whoops.fm7" that goes to a layout, then you are 
in luck. You can...

1) Create a second (temporary) file called "NeverDoThatAgain.fp7"
2) Go to ScriptMaker and create a new script
3) Add the step, Perform Script...
4) Click the Specify button
5) Choose "Add File Reference..." from the drop-down menu at the top of the 
Specify Script Options box. Select "Whoops.fp7"
6) Select the script which goes to a layout
7) Save it all and run the script.

When you run the script, FileMaker will open Whoops.fp7, immediately close 
the window, and then go to the layout specified. The file will be open but 
hidden.

You can then go to the Window menu, and choose Whoops.fp7 from the Show 
Hidden menu item. Voila! Your database is back.

There might be other Script steps (in Whoops.fp7) that will accomplish this 
but I tested the "Go to Layout" one and I know it works.

Bill

<ads@mayogenuine.com> wrote in message 
news:1107144730.797306.44020@z14g2000cwz.googlegroups.com...
> Whoops!
>
> I put:
>
> Close Window [Current Window]
>
> as the first line of my startup script. Now, the file closes the moment
> I open it. How do I recover? I tried the Escape key and cntl-f8. No
> luck.
>
> I am using FM7.0v3 on WindowsXP
>
> Thanks,
> Tony
> 

I found the clue in an old post:
> You might try opening another file and then running a script opens
your
> target file followed by Halt Script.
>
> John Weinshel
> datagrace
>
>
I tried this in FM7. It did not work by itself, but it did slow things
down enough for the Escape key to be recognized. Thanks!
Tony

John wrote:

ads@mayogenuine.com wrote:
> Whoops!
>
> I put:
>
> Close Window [Current Window]
>
> as the first line of my startup script. Now, the file closes the
moment
> I open it. How do I recover? I tried the Escape key and cntl-f8. No
> luck.
> 
> I am using FM7.0v3 on WindowsXP
> 
> Thanks,
> Tony

As a general technique, I've been including a Shift key detector in all my
startup scripts (FM 6.0):

If (Status (CurrentModifierKey) = 1)
     Halt Script
   Else
     Do all your startup stuff
EndIf

If troubleshooting is needed on a script or file that will immediately
close itself after launching, open it with the shift key held down and it
will avoid doing the rest of the closing script.

Steve Brown


In article <1107144730.797306.44020@z14g2000cwz.googlegroups.com>,
ads@mayogenuine.com wrote:

>Whoops!
>
>I put:
>
>Close Window [Current Window]
>
>as the first line of my startup script. Now, the file closes the moment
>I open it. How do I recover? I tried the Escape key and cntl-f8. No
>luck.
>
>I am using FM7.0v3 on WindowsXP
>
>Thanks,
>Tony

I suggest you consider the condition of the Caps Lock key as well:

If (Status (CurrentModifierKey) = 1 or Status (CurrentModifierKey) = 
3)

<eyebrown@mindspring.com> wrote in message 
news:eyebrown-0202050754560001@sdn-ap-010tnnashp0400.dialsprint.net...
> As a general technique, I've been including a Shift key detector in 
> all my
> startup scripts (FM 6.0):
>
> If (Status (CurrentModifierKey) = 1)
>     Halt Script
>   Else
>     Do all your startup stuff
> EndIf
>
> If troubleshooting is needed on a script or file that will 
> immediately
> close itself after launching, open it with the shift key held down 
> and it
> will avoid doing the rest of the closing script.
>
> Steve Brown
>
>
> In article <1107144730.797306.44020@z14g2000cwz.googlegroups.com>,
> ads@mayogenuine.com wrote:
>
>>Whoops!
>>
>>I put:
>>
>>Close Window [Current Window]
>>
>>as the first line of my startup script. Now, the file closes the 
>>moment
>>I open it. How do I recover? I tried the Escape key and cntl-f8. No
>>luck.
>>
>>I am using FM7.0v3 on WindowsXP
>>
>>Thanks,
>>Tony 

Or to simplify my typing, I always use this to allow me to hold the 
Control key, whether or not the caps lock is on:

If[ Status (CurrentModifierKey) >= 4 ]



Glenn Schwandt wrote:
> I suggest you consider the condition of the Caps Lock key as well:
> 
> If (Status (CurrentModifierKey) = 1 or Status (CurrentModifierKey) = 
> 3)
> 
> <eyebrown@mindspring.com> wrote in message 
> news:eyebrown-0202050754560001@sdn-ap-010tnnashp0400.dialsprint.net...
> 
>>As a general technique, I've been including a Shift key detector in 
>>all my
>>startup scripts (FM 6.0):
>>
>>If (Status (CurrentModifierKey) = 1)
>>    Halt Script
>>  Else
>>    Do all your startup stuff
>>EndIf
>>
>>If troubleshooting is needed on a script or file that will 
>>immediately
>>close itself after launching, open it with the shift key held down 
>>and it
>>will avoid doing the rest of the closing script.
>>
>>Steve Brown
>>
>>
>>In article <1107144730.797306.44020@z14g2000cwz.googlegroups.com>,
>>ads@mayogenuine.com wrote:
>>
>>
>>>Whoops!
>>>
>>>I put:
>>>
>>>Close Window [Current Window]
>>>
>>>as the first line of my startup script. Now, the file closes the 
>>>moment
>>>I open it. How do I recover? I tried the Escape key and cntl-f8. No
>>>luck.
>>>
>>>I am using FM7.0v3 on WindowsXP
>>>
>>>Thanks,
>>>Tony 
> 
> 
> 

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg              (818) 883-2846
FM Pro Solutions       Los Angeles, California

FileMaker 7 Certified Developer
Associate Member, FileMaker Solutions Alliance

In version 6, I just create a temp file with a relationship to other 
files that contain startup scripts. When I open the temp file, and go to 
the "define relationships" menu choice, it opens the related file(s) 
without triggering the startup script.

I don't know if that will still work in 7, but would appreciate finding 
out if anyone cares to test it.

Thanks

Kent

ads@mayogenuine.com said the following on 1/30/05 22:12:
> Whoops!
> 
> I put:
> 
> Close Window [Current Window]
> 
> as the first line of my startup script. Now, the file closes the moment
> I open it. How do I recover? I tried the Escape key and cntl-f8. No
> luck.
> 
> I am using FM7.0v3 on WindowsXP
> 
> Thanks,
> Tony
> 

This won't work so well in 7.  Though your method worked in 6, it was 
sort of a potential security issue.  In 7, the startup script will 
always run the first time a window from that file is brought to the 
foreground.

KV wrote:
> In version 6, I just create a temp file with a relationship to other 
> files that contain startup scripts. When I open the temp file, and go to 
> the "define relationships" menu choice, it opens the related file(s) 
> without triggering the startup script.
> 
> I don't know if that will still work in 7, but would appreciate finding 
> out if anyone cares to test it.
> 
> Thanks
> 
> Kent
> 
> ads@mayogenuine.com said the following on 1/30/05 22:12:
> 
>> Whoops!
>>
>> I put:
>>
>> Close Window [Current Window]
>>
>> as the first line of my startup script. Now, the file closes the moment
>> I open it. How do I recover? I tried the Escape key and cntl-f8. No
>> luck.
>>
>> I am using FM7.0v3 on WindowsXP
>>
>> Thanks,
>> Tony
>>

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg              (818) 883-2846
FM Pro Solutions       Los Angeles, California

FileMaker 7 Certified Developer
Associate Member, FileMaker Solutions Alliance

Thanks Howard. The issue hadn't occurred to me as I've never had to 
worry about security in the few solutions I manage. If I do get around 
to moving to 7, I will have to rethink my "no escape" design.

Kent

Howard Schlossberg said the following on 2/05/05 11:32:
> This won't work so well in 7.  Though your method worked in 6, it was 
> sort of a potential security issue.  In 7, the startup script will 
> always run the first time a window from that file is brought to the 
> foreground.
> 
> KV wrote:
> 
>> In version 6, I just create a temp file with a relationship to other 
>> files that contain startup scripts. When I open the temp file, and go 
>> to the "define relationships" menu choice, it opens the related 
>> file(s) without triggering the startup script.
>>
>> I don't know if that will still work in 7, but would appreciate 
>> finding out if anyone cares to test it.
>>
>> Thanks
>>
>> Kent

If you have developer, the script debugger can be helpful in this 
situation.  Just abort the script as soon as the debugger window appears.

KV wrote:
> Thanks Howard. The issue hadn't occurred to me as I've never had to 
> worry about security in the few solutions I manage. If I do get around 
> to moving to 7, I will have to rethink my "no escape" design.
> 
> Kent
> 
> Howard Schlossberg said the following on 2/05/05 11:32:
> 
>> This won't work so well in 7.  Though your method worked in 6, it was 
>> sort of a potential security issue.  In 7, the startup script will 
>> always run the first time a window from that file is brought to the 
>> foreground.
>>
>> KV wrote:
>>
>>> In version 6, I just create a temp file with a relationship to other 
>>> files that contain startup scripts. When I open the temp file, and go 
>>> to the "define relationships" menu choice, it opens the related 
>>> file(s) without triggering the startup script.
>>>
>>> I don't know if that will still work in 7, but would appreciate 
>>> finding out if anyone cares to test it.
>>>
>>> Thanks
>>>
>>> Kent