ok i have been busy redoing a lot of the code....
the form intermittently does the aforementioned initial problem now. VERY strange indeed.
I will attempt to redo the entire code for the form that is looping for no apparent reason in the next day or two.
Now to answer a few questions....
the "1" was used before when I was actually looking to see if a file that held the encrypted password was there or not. If it wasnt there, then "goto 1," which ended the procedure. But now I'm not using a file to store the encrypted password. I am writing it to the registry instead (also encrypted). Much better this way imho.
the Pause in the code was (and still is used) if a password has been previously entered in to load the next form. The reason i used the Pause was because the GUI looks kinda cool and it allowed for a little time for the user to see what is actually happening. The Pause is now set at 2 instead of 1.5.
Also, the Pause is a valid command since I have code to actually count (in seconds instead of milliseconds) in a separate procedure/subroutine.
Lastly, I have tried an 'unload form' already to no avail because as it loops, it simply reopens the form that was unloaded. I tried that before i posted this problem here. Good suggestion however.
Hope that clears some things up. The problem is still not solved though. :\
Thanks for the help very much. Im sure eventually it will get it figured out. Hopefully sooner than later.