Discussion:
files locked for more than one user
(too old to reply)
mmac
2004-10-03 17:29:23 UTC
Permalink
vfp6 - I have never had a problem with file locking while using foxpro but
for some reason, in a current app I have written, after the app is opened on
one machine, trying to open the app on any other machine fails due to the
database being locked. Set locks is off. Any Ideas ??? Platform is XP pro
in a workgroup enviroment. Help?
Stefan Wuebbe
2004-10-04 08:08:29 UTC
Permalink
At which point do you get what error message/number exactly?
Post by mmac
Set locks is off.
Do you mean Set('Exclusive') is off? As a guess, a typical scenario for
Error 1705 in that case might be that a form with private datasession is
the first to open the database.dbc at runtime.
If so, Set Exclusive will be On by default, scoped to the current
datasession (unless you Set Exclusive Off in DE.BeforeOpenTables()
See also "SET DATASESSION Command" in help.
You can Open Database xy Shared explicitly beforehand somewhere
early in your "main.prg" to avoid that effect.


hth
-Stefan
Post by mmac
vfp6 - I have never had a problem with file locking while using foxpro but for
some reason, in a current app I have written, after the app is opened on one
machine, trying to open the app on any other machine fails due to the database
being locked. Set locks is off. Any Ideas ??? Platform is XP pro in a workgroup
enviroment. Help?
Fred Taylor
2004-10-04 15:19:16 UTC
Permalink
Sounds like the first machine is opening things exclusively. Do you have a
SET EXCLUSIVE OFF in the beginning of your application?

Fred
Microsoft Visual FoxPro MVP
Post by mmac
vfp6 - I have never had a problem with file locking while using foxpro
but for some reason, in a current app I have written, after the app is
opened on one machine, trying to open the app on any other machine fails
due to the database being locked. Set locks is off. Any Ideas ???
Platform is XP pro in a workgroup enviroment. Help?
Loading...