Hi Wess,
This would not be an upgraded multi table form from 6.x would it?
I have found that converted forms want to jump to the next table regardless if
they are started with "Edit" or "Enter". This causes error messages with
constraints and rules in the first table. The only way I was able to resolve
the problem was to recreate the exact same forms from scratch in 7.x
I found the problem by removing the rules and constraints and then noticed the
immediate jump to the second table.
If it helps any, I opened two sessions of version 7.x and copied the objects
and variable expressions from the "broken" form in one session to the new form
in the second session. You can actually select a whole batch of objects at one
time and copy them , then paste them into the new form. The new one worked
fine.
Not a "happy" answer but I hope it helps.
:-)
Michael
Michael Moser
EXAQ Micro Services
www.exaq.com
Phone: 916-966-8313
Fax: 916-966-8313
>> Hey Folks...
>> Another quick question on upgrading to 7.1:
>> I have tables with fields defined as "not null". Under 7.1, when I try to
>> enter a row (using a form) in these tables, I get the "Field X cannot be
>> null" message as soon as I open the form. Shouldn't I only get that
>> message when I try to save the row?
>> I don't want to remove my not null constraints on these rows. They are
>> too important...
>> Help! {:{)}
>> Thanks!
>> --W