From: Rob Vleeschhouwer
To: Andy Kramek
Hot Springs Village
Arkansas - United States
Visual FoxPro 9
Databases, Tables and SQL Server
Thursday, August 30, 2007 10:41:30 AM
This message was rated by:
> > This will work for sure. No need to try. But I want to know why myfile1 gives no problems,
> > and myfile2 does.
> Because you obviously have the tables open BEFORE you issued SET EXCLUSIVE ON (you are using SELECT myfile1 and SELECT myfile2 which does not actually open the tables) - presumably the first was already exclusive, but the second was not.
> Remember that changing the setting of EXCLUSIVE does not affect anything that is ALREADY open - it only affects things explicitly opened after the setting changed - which is why Mike's solution works and your didn't.
> Andy Kramek
> Microsoft MVP (Visual FoxPro)
Tightline Computers Inc, Akron Ohio, USA
In fact the command 'set exclusive on' is allready in the main programm. And nowhere
there is a 'set exclusive off'
I do not want to spend a lot of time to it. I use now 'delete all' instead.
I know the concequenses of that.
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