fp and windows 7

[Del]

I just converted to Win 7 64bit, and filepro moved over and ran with no 
immediate problem.
However, the filepro manual (I forget, was that one of John's things?) would 
only run in XP mode.

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.
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.


Del

-----Original Message----- 
From: Kenneth Brody
Sent: Friday, May 20, 2011 12:05 PM
To: davidrottkamp at echoes.net
Cc: filepro-list at seaslug.org
Subject: Re: fp and windows 7

On 5/20/2011 9:38 AM, davidrottkamp at echoes.net wrote:
> Hi Everyone
> I have a windows client using filepro 5.0.03 on XP box
> He just purchased a windows 7 box (64bit)
> trying to run filepro on windows 7 , changed p.exe to run in xp compatible 
> mode
> and still get message box saying
> The version of this file is not compatible with the version of windows you 
> are running. Check to see if you need an x86 (32 bit) or x64 (64 bit) 
> version of the program.
> ideas , suggestions appreciated

I have 64-bit Windows 7, and have no problems running older versions of
filePro.  The only time I get such an error is if I try running an ancient
MS-DOS version of filePro.  (Or, for that matter, an ancient MS-DOS version
of any executable I have.)  I don't know if it's a Windows 7 thing, or a
64-bit Windows thing.  (My 32-bit Windows Vista would still run 16-bit
MS-DOS apps.)

Is it possible that they are still using an ancient copy of p.exe?  (What's
the date and size of p.exe?)  What happens if you try running dclerk 
directly?

-- 
Kenneth Brody
_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
Subscribe/Unsubscribe/Subscription Changes
http://mailman.celestial.com/mailman/listinfo/filepro-list