From: Massimo Tombesi
To: Rob Vleeschhouwer
Visual FoxPro 9
Databases, Tables and SQL Server
Monday, August 27, 2007 2:50:51 PM
This message was rated by:
> In one procedure:
> set exclu on
> set safety off
> select myfile1
> select myfile2
> zap myfile1 gives no problems
> zap myfile2 gives an error: file must be opened exclusive.
> zap first myfile2 gives the same error.
> set exclu off gives the same result.
> So I think it must be something in the table itself, but don't know what.
Perhaps because SET EXCLUSIVE can't change the status of previously opened tables, like that you are SELECTing. This may happen when you SELECT a table that is already open with the clause Exclusive=.F., for example in the dataenvironment of a form. If this is the case, you have to issue SET EXCLUSIVE ON before opening the table (or in the dataenvironment), and not just before you SELECT it.
Posted by Rob @ 8/26/2007 1:41:36 PM
Posted by Mike Gagnon @ 8/26/2007 2:18:12 PM
Posted by Rob @ 8/27/2007 1:50:26 PM
Posted by Andy Kramek @ 8/27/2007 2:30:39 PM
Posted by Rob @ 8/30/2007 10:41:30 AM
Posted by tushar @ 8/30/2007 10:44:05 AM
Posted by Rob @ 8/30/2007 11:26:19 AM
Posted by Rob @ 9/3/2007 6:17:17 PM
Posted by Ken Murphy @ 9/3/2007 6:37:03 PM
Posted by Rob @ 9/3/2007 7:09:05 PM
Posted by Ken Murphy @ 9/4/2007 1:19:09 AM
Posted by Andy Kramek @ 8/30/2007 1:07:00 PM
Posted by Rob @ 8/30/2007 7:58:17 PM
Posted by Massimo Tombesi @ 8/27/2007 2:50:51 PM
Posted by Cetin Basoz @ 8/30/2007 1:19:23 PM