>>Greetings all...I've read alot about ERROR #1104, and how it boils down to a network connection problem most of the time. In my situation, this must be true, but I find that while my clients must have lost connection for a brief ammount of time, that they can close the app and then re-open it and everything is fine...my question, is there a way to test for #1104 and then execute some code to reconnect to the database?
>> I agree that the best thing is to find the root cause, but in my case, this is a slow process, and until then I think it'd be worthwhile to make my app even more bulletproof!!:) Any suggestions?
>
>Don't even think about writing code to "get around" an intermittently bad network connection. You lose the connection, all bets are off. Get your clients to fix their network. If you're firm about it, eventually they will thank you for it!

Thanks AL...however, in this case, my client is my boss...I'm trying to persuade them to look closer at this...but it's slow going...anyway, I think I might be onto something...but I'd like to hear any ideas anyone may have...but assume this, getting the network fixed is not an option...yeah I know, what a hassle, but I believe this can only make things better.