64-bit Windows continued

[Ryan Powers]

> What version of filePro are you running?  This is from the 5.0.09 readme:

5.0.09DN9

> > (Windows network only) #570
> >
> >     It was possible that, if one process was accessing an index for the
> >     first time and another was reading/writing the head of that index at
> >     the exact same time, the read/write process would get a Windows
> >     locking violation (Windows error #33)


Apparently it hasn't bothered him much over the years. It has only now
cropped
up due to it being at a crawl, I would think.

Here are some more thoughts on the issue from the client:

<quote>

In filepro 4.5 (I believe) they added a "-p" flag for lookups, in which it
protects the record during the lookup.   It states in their documentation
that this is a UNIX only function (I understand that to mean it is not used
in the PC world, therefore I've never used it.)   Could you find out if
other programmers [use] this in the PC world, and if so, what results they
have seen?

Also, there is a flag you can add to the rreport command (-ro) that forces
it to be read-only.   There is also an environment variable PFREADONLY that
accomplishes the same thing.    During much of the report functions that
we're running, the lookups are for reading from the file only....i.e., we're
not updating any information in the looked up files, simply running reports.
I'm thinking out loud here ....I'm wondering if I changed the lookup
statements or run reports using the -ra flag, would the O/S allow multiple
sessions to run simultaneously on the same records because they are
read-only (essentially eliminating the error message in the screen shot).

</quote>



---
Ryan Powers
Bulldog Software, Inc.
http://www.bulldogsoftware.com