fp and windows 7

[Kenneth Brody]

On 5/20/2011 3:48 PM, Del wrote:
[...]
> Anyway, I have a question about lockfile creation in windows.
> I frequently kill or delete lockfiles in scripts or from within a process
> using "ddir filename -m qualifier -l"
> This physically deletes the lockfile for that qualifier.
> In SCO Unix, where I have most of my experience, when you then enter the
> file via dclerk or dreport, a new lockfile is immediately created.
> However, this does not appear to be true in windows, based on testing that I
> have just done.
> The lockfile is NOT recreated when I update the file with dclerk or run a
> report.

Then something is seriously "broken" with your system.  (Or you have a 
single-user MS-DOS version of dclerk and dreport, which could be considered 
a form of "broken".)  Immediately upon entering virtually any filePro 
program, and giving it a filename, the lockfile will be created if it didn't 
already exist.  Windows is no different than *nix in this respect.

What is the exact version of dclerk you are running?  And, if you open two 
dclerk windows, and attempt to update the same record in the same file at 
the same time, what happens?

> The only way I got a new lockfile to appear in the data directory in Windows
> filepro (both XP and Win 7) was to go in via the filepro directory and
> delete the lockfile (which was not there because it was already deleted).
> This created a new lockfile, presumably after attempting to delete the old
> one.
> I am worried that users running reports or updating files would not be
> re-creating lockfiles that I may have deleted with the ddir command.
> Lockfiles are there for a reason, after all.
[...]

-- 
Kenneth Brody