>A client just reported a situation where a user is getting a "cannot update table because it is read only" error when the application starts up. The table is FOXUSER, which is on his C: drive (the app is run from the network). But then he can go in and edit data just fine, so the main tables aren't read only. In another app I wrote for them, he gets a "resource file is invalid, overwrite it with a new one?" message. He can click yes and continue, but then gets an error saying that another table is read only and can't be updated (this is a small housekeeping table located on the network). He can continue past that and use the program normally. Other users are not experiencing these errors and these programs have been in place for years. This is an XP machine (XP being new their network, they tell me) and the IT Mgr is super strict (overly strict, IMHO) on security. We've run into problems with that in the past because things are buckled down so tightly, however it didn't affect
>just some tables and leave others operating normally. Naturally, we don't have the files set to read only, so I'm not sure why VFP would exhibit this behavior, but I suspect security settings. Anyone have any thoughts on this?
>
>Russell Campbell

Not quite clear, do you allow user to update FOXUSER table from your code ?FOXUSER is the name of the foxpro resource file by default.