Oops! Can I disable start-up script?

[Wickerman]

Boy do *I* feel silly. I'm trying to use a splash screen for the first time, identifying the database name and my contact info, so I made a script that opens the splashscreen layout, but when i tried it, I found the last layout viewed also opens.

So, I took a guess and put a "Close Window" step at the beginning of the script, which is apparently the wrong thing to do, since now when I open the file, it immediately closes the window and I'm left with no open file . . . which means I can't get back in to fix the script. In effect, I'm barred from entry to my database! D'oh!

I figure there must be a way to circumvent the opening script, yes? Please? Holding some arcane combination of buttons down? I'd appreciate any help, and maybe a pointer to a good overview of how to properly script an openign splashscreen.

Wickerman

[Søren Dyhr]

Why circumvent, why not put in a condition looking via Get(UserName) or Get(PrivilegeSetName) if the init script should be exited??

--sd

[normanicus]

As far as I remember if you create another fp7 file and do a GTTR to a related record in the problem file then the startup script is not run.

[Wickerman]

Ahhh -- the GTRR workaround got me back in a-ok - thanks!

albert

[softpac]

What's a GTTR?

[bcooney]

GTRR = go to related records

[softpac]

Reason I ask is because I've done the same thing - locked myself out and now I to disable the opening script. But I don't follow/understand the solution offered here. Your help is much appreciated.

[Wickerman]

Hi Softpac -- since I benefited from the original suggestion, I'll pass it along.

Create a new database file (or open an existing one you haven't locked yourself out of). Create a relationship between any field in your available file and some field in your inaccessible file and then put a button on a layout formatted to "Go to Related Records" and identifying any related layout from your inaccessible file. THen go into browse mode and click the button -0- *voila* you're back in your other file, where you can disable the problem script.

Wickerman

[softpac]

Thanks for that!

[_henry_]

Hi Wickerman,

Is that method only work for a FM file that still has the Admin access to the file (Admin's privilege has not been removed)?

Thanks for the answer in advance

[Wickerman]

Hmmm -- I don't know about that one. To date, I haven;t monkeyed with access / permissions much. Anyone else shed light on this one?

Wickerman

[Tissot]

No!

Regards

Ron

[GeoSteven]

I know I'm jumping in late here but I ran across this thread looking for something else. My answer to your issue seems simpler to me. Create (or open) any other database. Set script debugger on. Open 'locked' database. Go to scriptmaker from the debug window. Remove offending script step. Save... :