>Hi friends:
>
>A few years ago I started having troubles because the error message in English should be: "The file namefile can't be updated because is readonly" and as I posted this before someone told me "that must be an antivirus" since that I use to check the antivirus and make an exception for my datafolder.
>
>If I am here posting this again you should suspect that wasn't the solution.
>
>The last I did was to include "IF READONLY()" just before add or modify a record and.. READONLY() returns .T.!!!
>
>I swear I don't open any file with the readonly clause...
>
>Any idea?
>
>TIA.
>
> Héctor

Another thing to watch out for is the directory in which application has been installed (assuming that the tables are in the same path as the program) -- in particular if the program is installed in something like "c:\program files" or "c:\program files (x86)". Generally wasn't a problem back in the Windows XP/Server 2000 days, became a problem starting with Windows Vista/Server 2003 when access rules became enforced. This combined with the directory virtualization feature could result in a potential "gotcha" -- especially in a case where you've got multiple users that need to be accessing a common set of tables.
On a networked copy, you may want to check *both* the Security and Sharing tab for the folder to make sure that write access is being granted on each of these pages.
Yet another thing to be careful about are situations where you might reference a table in a SQL query -- if the table wasn't open at the time you execute the query, this table will be automatically opened -- in read-only mode.