I *think* that W2K and XP both have a limit on the number of "shares" of 10.

Could it be that the limit is reached by the combination of # workstations accessing the W2K system and the shares they allocate (like printers and who-knows-what-else too)?

If, when you say logoff and log in again you mean out of the OS and back again, I could see that dropping the share count.

Not sure the error described is the correct one for what I suggest, but...

good luck


>Hi
>
>Table causing problem is open in shared mode - that's why it's so curious - it's also been functioning without this problem for 2 years and has suddenly started happening - no recent mods to this application
>
>Colin
>
>>Hi Colin,
>>
>>If you are opening the table in EXCLUSIVE mode then you get this error. If you are sharing the data across the network, you should open your tables in SHARED mode. Do you know what file is being used? Is it a production table, or maybe you are creating temp tables during an operation that is causing the problem? These are the things you should look at.
>>
>>If it is the temp tables, then you are probably creating them on a networked drive, or even maybe, creating the temp table twice in the same user session without "cleaning up" your workspace when an operation is complete.
>>
>>HTH
>>
>>
>>>As users log in to a VFP6 application - many of them get the error message File in use by another - they log out and log in again and it's ok - some users never get the problem at all
>>>
>>>All users running Windows XP are using local exe and work files and are tring to get access to a table on another machine running Windows 2000 SP4
>>>
>>>Anyone have any idea why this error occurs and what to do about it?
>>>
>>>Thanks
>>>
>>>Colin