I just came across something and before I enter it in issuetaker wanted
to make sure this wasn't the intended bhavior. In which case I
will enter an RFE.
Created a table with 4 columns. Native base database.
Created an embedded form against this table with 4 text controls, bound
to the columns.
Closed the form.
Edited the table and dropped the 3rd column from the table.
Opened the form, data entry mode.
The form does not report any problem. The control is left active and
will receive input from the user. The problem is
that the bound column is gone, so the data has no place to go.
This doesn't seem correct to me. Look at it another way. I use base to
create some forms against a corporate
database. Later I open that form, the DBA has altered one of the tables
and a column is gone. If I am browsing the
records it would simply appear that this column is NULL.
It would seem to me that the system should at a minimum warn the user
that a bound column is no longer available, or
perhaps disable the control, or both.
Question is, was this the design - the quiteness?
Thanks
Andrew 'Drew' Jensen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
