Automatic and locking (was RE: -RO causes an error)

[Kenneth Brody]

Quoting John Esak (Fri, 3 Jun 2005 15:01:23 -0400):
[...]
> <beating a dead horse department>
> Actually, it is not just bad form... it is bad programming, period. By
> the time you are on the automatic table for _any_ reason... the record
> is *unlocked*.

That's not quite true.  (The "for _any_ reason" part, that is.)

When entering update mode, automatic will be run _after_ the record
has been locked.

Also, during the output phase of *report, the record is locked when
automatic is run.

> Therefore, doing any kind of assignment to a real field
> *in-the-current-file*, with or without a WRITE statement... is just
> plain bad programming and since the record is not locked, niether are
> the indexes... and everything is just doubly wrong for "writing to the
> curent record on the automatic table".

I took the original post to mean modifying lookup fields in the
automatic processing, which is fine as far as filePro is concerned,
as long as the the lookup is potected.  (Though it may be considered
"bad form" by most people.)

> Writing to another file other than the current file while on an
> automatic table is *bad form*. :-)
>
> John Esak
>
> </beating a dead horse department>

Shouldn't you close the tag _before_ your name?  :-)

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