Record locking

[John Esak]

> used the word SHOW, and not "post code", since I, myself, can't
> necessarily
> duplicate the problems at some of my other filePro Windows customers.

Well, okay, sorry. I just thought you meant put it up here rather than have
me come to the midwest. :-)
hard drive caching problems on the faster IDE hard drive


> controllers, where
> the files aren't written to the hard drive properly before my 2nd report
> begins.  I have learned that I have to "space apart" my *report
> commands in
> the scripts with some other program, such as rebuilding an index on an
> entirely unrelated filePro file.  If I do that between each *report line,
> then the reports will all run correctly.  PFSYNC also helps on network
> systems.
>
> 	This is another example of something that was discussed a couple or
> times on the list a few years ago, and we came up with a work-around.  I
> don't know if it is fixed on filePro 5.0.13, but I suppose I
> could test that
> again, too.
>

But Mike, again do you see how this sounds... You say there is some problem
(or you think) there is some problem dealing with controlers, writing disk
cache etc... then you state you don't know whether it is fixed on 5.0.13 or
not... How the heck could filePro fix a problem like you mention???  It is
not filePro's problem, and that is all I am trying to keep clear.

John

Hey you haven't been in the FP Room for awhile. Hope all is okay.


visit the FP Room www.tinyurl.com/yuag7 24/7