Thanks for the suggestions everyone. We already use ON ERROR and a class to open tables. I'm working on a web app right now that multiple clients use. I've been trying to crash it, so I created a text file, test.txt and renamed it to test.dbf. I found that when the code tried to open the invalid table ON ERROR worked and it didn't crash. But tables that were opened before I tried to open the invalid table were closed - so it did crash, but further along in the code when it tried to select a table that was previously open. I recently inherited this app so I'm still learning how it works. This morning I found another ON ERROR command that doesn't get called when you are in development mode. When the second ON ERROR command is set the second error is trapped and the app does not crash. And our error table and log files have enough information in it so I can figure out why the error occured. So I'm happy now. :)

>>Hi,
>>
>>Is there a way to check if a VFP table is valid before trying to open it? Using VFP 7.
>
>
>Hi Chris,
>
>There're a few MS KB articles about this:
>- http://support.microsoft.com/default.aspx?scid=kb;en-us;110968
>- http://support.microsoft.com/default.aspx?scid=kb;en-us;263902
>- http://support.microsoft.com/default.aspx?scid=kb;en-us;293638