64-bit Windows continued

[Kenneth Brody]

On 8/19/2011 11:45 AM, Ryan Powers wrote:
> The issue remains unresolved. After trying everything, the tech is at a loss
> as to what is causing more than one user to cause filePro to slow to a
> crawl. The have shut down the anti-virus, replaced routers, cables, and many
> others to no avail. Now they are getting a fatal error from rreport as
> follows:
>
> *** A System Error Has Occurred ***
> /filepro/mvmultic/index.A: Error Number -1
> Windows error #33
> The process cannot access the file because another process has locked a
> portion
> of the file.
>
> My client says that he has this file running in zillions of client/server
> offices and has never had any problems.
>
> The Windows-64 guy now sounds convinced that it isn't *his* problem and that
> it's most likely filePro's fault. Any suggestions?

Well, filePro has no issues on my 64-bit Windows system.  Nor has anyone 
else within fPTech had problems with it on their 64-bit Windows systems.

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

> (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)

-- 
Kenneth Brody