>>Ocassionally, my application loses its connection to the network. (The Infamous Drive G does not exist, Abort, Retry, Ignore.)
>>
>>Is there any way of trapping for this error. I have an on error routine, but this stops the application from running. Usually all you need to do is hit Retry and awy it goes..
>>
>>I am trying to track down, why it is loosing the network connection, but until I find this out, is there a trap that I could add, so that the application will retry all on its own.
>>
>>(The application is written, such that it performs the correct mappings on boot up.)
>
>If this is on a Novell network AND the client is running DOS, the client can be configured to automatically reconnect when a network error occurs via NET.CFG. Alternately, you could try to lock the table [lock()/rlock()] until successful - tho this may not be practical if others are using it...
>
>If you need more information on bulletproofing NET.CFG, let me know.
>
>HTH,
>Paul M.
I can use the info on net.cfg for my files... however, the software is running on a Novell server... it is not this server that it keeps loosing its connection to.

The network it is on has also got an NT server. One file must reside there... This is the root of the problem. The above error occurs when trying to write to the NT server.


Thanks a lot,
Mike