On Unload and current record - bug/feature/one of those

Bill Hutten (6/11/14 11:45AM)

Bill Hutten (6/11/14 11:45 AM)

things?

I can't believe I've never noticed this before. A test database, one
table:

FORM SET INPUT([Test];"Input")
FORM SET OUTPUT([Test];"Output")
ALL RECORDS([Test])
MODIFY SELECTION([Test])

If there is more than one record 4D will display the records in the
output form, you double-click, etc. If there is only one record 4D
directly displays the input form. So far, so normal.

Now - if 4D starts from the output form (that is, there is more than
one
record in the selection) - then there is no current record in the "On
Unload" phase ("Record Number([Test]) returns -1). However, if there is
only one record in the selection and 4D directly displays that one
record, then in the "On Unload" phase the record stays loaded until "On
Unload" finishes executing.

I see this in 2004 all the way through 13.5, so it's clearly not a
recent bug unless I'm really missing something.

Is this behaviour documented anywhere? Do other people see this?

- bill

Reply to this message

Summary created 6/11/14 at 11:59PM by Intellex Corporation

Comments welcome at: feedback@intellexcorp.com