Hi George and Ed,

Thanks for your replies.

Good News on the elimination of the c5 error. Deleting the foxuser.dbf gave gave us a partial success. However, removing a bitmap from the report eliminates the c5 error for all work stations.

I'm going to let the users use the system without the bitmap on the report for a week or so to see if the problem has really gone. The bitmap file is not corrupted. It comes up in MS Paint with no problem.

I got the idea to get rid of the bitmap from a note by Bonnie B. about C5 errors and bitmaps on forms. I also looked at the Dr. Watson log on the clients' nt workstations. The name of the bitmap was there in the "raw stack dump" along with the names of other files. I run Win95 at home and don't have Dr. Watson.

Thanks again for your help.

Paul


>>Hi George,
>>
>>I've had some success. I reviewed all the c0000005 references at the UT since January. Ed Rauh described problems in foxuser.dbf and the Watch window in the debugger.
>>
>>One client has VFP 5.0 on their machine. I asked the client to delete all records in the foxuser.dbf in the home directory of my application on her machine. She is running the application from an exe.
>>
>>She hasn't had a problem with my application in three days of intensive use.
>>
>>We tried the same technique on other workstations with partial success.
>>
>>I'm wondering if I can safely delete all records in all instances of foxuser.dbf on my clients workstations?
>>
>>I have not had time to try the other fixes we talked about. Since I'm getting partial success with this foxuser.dbf, I probably continue on this path for the moment.
>>
>>Thanks again,
>>
>>
>>Paul
>>
>As Ed mentioned, there's the option of setting RESOURCE to OFF. However, if you're allowing users to modify reports, that's probably not a good idea. VFP saves toolbar info in the foxuser table.
>
>To answer the question, however, the only thing you'll lose by deleting it is the user preferences that are stored there. The BROWSE LAST settings, system toobar information, etc. If that's acceptable, go and delete it.
>
>hth,