Shouldn't it be other way around: first, copy DBC localy; second, change connection?
>
>We are experiencing problems on our application. We deployed a client/server application in a server that contains an exe and a vfp database container. The connection string is stored in an xml file which the user can change using an application tool.
>
>Upon running the exe, the application will check if the connection string of the database container is equal to the connection string stored in the xml file. The system will then update the connection string of the DBC with the connection string stored in the xml file, then the dbc is being copied to a local folder a the client machine.
>
>The problem is, after several clients have run the system and successfully connected, the DBC automatically becomes read-only, causing an error when the system will update the dbc file.
>
>
>Any idea on how to trace this problem? By the way, we are using VFP9
>
>
>Thanks in advance...