Wickerman Posted December 18, 2007 Share Posted December 18, 2007 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 Link to comment Share on other sites More sharing options...
Søren Dyhr Posted December 18, 2007 Share Posted December 18, 2007 Why circumvent, why not put in a condition looking via Get(UserName) or Get(PrivilegeSetName) if the init script should be exited?? --sd Link to comment Share on other sites More sharing options...
normanicus Posted December 18, 2007 Share Posted December 18, 2007 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. Link to comment Share on other sites More sharing options...
Wickerman Posted December 18, 2007 Author Share Posted December 18, 2007 Ahhh -- the GTRR workaround got me back in a-ok - thanks! albert Link to comment Share on other sites More sharing options...
softpac Posted January 2, 2008 Share Posted January 2, 2008 What's a GTTR? Link to comment Share on other sites More sharing options...
bcooney Posted January 2, 2008 Share Posted January 2, 2008 GTRR = go to related records Link to comment Share on other sites More sharing options...
softpac Posted January 2, 2008 Share Posted January 2, 2008 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. Link to comment Share on other sites More sharing options...
Wickerman Posted January 3, 2008 Author Share Posted January 3, 2008 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 Link to comment Share on other sites More sharing options...
softpac Posted January 3, 2008 Share Posted January 3, 2008 Thanks for that! Link to comment Share on other sites More sharing options...
_henry_ Posted January 3, 2008 Share Posted January 3, 2008 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 Link to comment Share on other sites More sharing options...
Wickerman Posted January 3, 2008 Author Share Posted January 3, 2008 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 Link to comment Share on other sites More sharing options...
Tissot Posted January 17, 2008 Share Posted January 17, 2008 No! Regards Ron Link to comment Share on other sites More sharing options...
GeoSteven Posted March 11, 2010 Share Posted March 11, 2010 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... : Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 5131 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now