Thanks for your reply. I think it has something to do with insufficient privledges. The table is location in our "M:\" The user has full access to that location. But the project is in a location called "j:\mis\projects\projectname" (forms would be j:\...\forms) Users don't have access to "j:\" (but they do have access to the tables) We build the .exe into j:\mis\projects\projectname\name.exe. Then I copy that over to a different directory. (then I can work on it w/o disrupting users) We have just recently started using VFP 7, never had this problem in fp 2.6.

If I give the user full access "J:\mis\projects\.." then it will work. I am guessing that when you type the command "use m:tablename" it creates a cursor somewhere. I wonder if its putting it into "j:\..." because I set the default directory to that while development. Is there a way I can change where the cursor is created? I don't want to change the default directory otherwise commands like "do forms/frmForm" won't work. And I don't want to give users access to program files, etc.

Thanks,
Chris

>Sometimes, it seems to me, you should translate this particular message as "Table can't be updated".
>
>Just check for reasons why your table can't be updated, such as disk full, insufficient privileges, R/O, etc.
>
>HTH, Hilmar.