>I have been running the same code on a certain part of my program for a while now, with either no modifications, or only adding a few message boxes here and there on certain conditions as reminders to do certain things. The problem is that recently, at random times my code will pop up boxes on the users whom use this part of the program telling them that a certain file (table) does not exist, or an alias to a certain other table is not found, no table is open in the current work area, usually followed by the (form name) is not an object. The strange part about the program errors is that usually they are kicked out of the program, but the network (novell) is still connected and the drive is still there. They can even re-run the program and it will pull up fine without rebooting the machine or the need to reconnect to the network (it is already connected).
>
> What would cause my tables to randomly drop off like that? Is there any code I could put in to check for this and if so, make an attempt to establish connection with the tables again before trying to continue to process code where VFP has already released all the tables for some reason.

Sounds like some sort of intermittent network problem. Check the Novell system log to see if the server is detecting any problems (also check workstation event logs). Check electrical power quality everywhere, whether there is a loose or damaged cable, malfing switch or NIC, etc. If antivirus is present try disabling it (server and workstations).

As for checking for network disconnections - it is possible to write code that is as bullet-proof as possible and takes almost nothing for granted. However, network/connectivity problems happen at a lower level than your app. Trying to predict, then code against all possible failure modes is difficult to impossible. If at the OS level a network disconnect has been detected, it's likely that the local VFP data cache, Novell network client cache and/or server locks table for that connection are corrupted or lost. Even if you could get a table re-opened on some sort of RETRY, would you be happy with that? I think your best strategy would be to exit the program as gracefully as possible, and restart.

File-server databases move a lot of data over the wire, and so are dependent on a solid and properly-configured network. VFP has always pushed the hardware and networking "envelope" and is usually the first application to detect problems ;-)