Ola, Ricardo, (I can't find the a-with-accent)

One way around this is to store the DBC as a text file (using GenDBC or GenDbcX) then recreate it for each user. Replacing the text file is much simpler than worrying about locks, and the next time each user starts the program his 'personal' DBC will be recreated.

This won't work if you are using any local tables, but will if you're using just SQL-Server and remote views.

HTH
Barbara

>Hi,
>
>I work with remote views and SQL Server.
>Im my reconstruction routine, i delete the remote view, delete the table at SQL Server, create the same table (with new fields, etc), and... need to create the remote view for that new table.
>The problem is VFP blocks the system when i'm doing the CREATE SQL VIEW ... REMOTE CONNNECTION ...
>
>I've read VFP's help; here is one thing i've found at DELETE VIEW's remarks: If a SQL view is opened and then deleted, the cursors containing the SQL view results are not closed.
>
>I don't know if this is the problem. Any ideias???
>
>Thanks,
>
>Ricardo