Fw: one record overwrites another record

[Kenneth Brody]

Quoting Dennis Malen (Mon, 18 Sep 2006 20:15:40 -0400):

> We have used the same processing for many many years in 4.8. It never
> happened. We also went into 4.8 to try to replicate it and was not
> successful. It is not a problem in 4.8.

Well, without seeing the processing, we can only guess.

> Ken, it is not my processing but something peculiar to 5.0. I also
> understand that others have had the same problem and you have not been
> able to fix it.

I've never heard of this before.  If they've had "the same problem",
they certainly haven't reported it to fPTech, AFAIK.

> In any event, after many hours of trial and error we have fixed the
> problem by placing a -w on the lookup - line. For whatever reason it
> did not keep the info in the buffer to be improperly written to the
> other file. It is my understanding others have used another approach
> which is to have the lookup take place in @entsel.

All the "-w" does is tell filePro to fail a "-p" lookup if the record
is locked, rather than wait for it to become unlocked.  If the record
wasn't already locked by someone else, it makes no difference.  If the
record is locked by someone else, then the lookup will fail and you
can't access the lookup.  I have no idea what you mean by "it did not
keep the info in the buffer".

> Anyone who is interested I will be more than happen to share my findings
> and resolution in more detail. Please call me at the number below and I
> will be more than happy to discuss.

If you have what you feel is a filePro bug, why haven't you contacted
fpsupport and arrange to send files to them?

[...]

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com