>>I keep getting the following error, both while in development and when running an application:
>>
>>"Program Error:
>> VFP6.exe has generated errors and will be closed by Windows.
>> You will need to restart the program.
>>
>> An error log is being created."
>>
>>I just recently started with this company, who has a mainframe located in Chicago where several Oracle and DB2 databases reside. My new job requires that I gather lots of data from these databases. I haven’t had a lot of experience with non-native databases in the past. My predecessors used SQLCONNECT and SQLEXEC to handle this function. I’ve converted some of the processes to Remote Views stored in a DBC containing named connections with a named data source, userid, and password.
>>
>>When working in development I seem to be getting the error when I go to modify one of my views. I’m also getting the same error when running an application which uses the SQLCONNECT and SQLEXEC functions. It’s hard to tell what causes the error when running the application, there doesn’t seem to be any pattern. Several end-users are also getting the error when running the application.
>>
>>I'm guessing it has something to do with the connection timing-out between the database.
>
>Probably the most common cause of fatal errors (usually C0000005) in VFP is bad video drivers. In your case I'd install W2K SP4 and the latest updates, then make sure you're running the latest video driver for the exact hardware you have.
>
>Other possibilities:
>- bad FOXUSER table - try renaming yours, let VFP build a new one and see if the problem persists
>- subtle .DBC problem - you could try opening it as a table and issuing REINDEX to rebuild the .DCX index
>
>There are many other less common causes you can find by searching messages here (e.g. "C5 error") or on the Fox Wiki ( http://fox.wikis.com/wc.dll?Wiki~FoxProWiki ).

I don't think it's the video driver or FOXUSER table because every user is getting it.

I also don't think it's the .DBC because it happens whether I'm modifying the views or using the SQLCONNECT function.

I really think it has something to do with the database connection. I'm doing something out of order, not disconnecting properly, the database is timing-out, etc.

Thanks,