Razzak helped me out with that just the other night....I had spent hours trying to figure out what was a "corrupted" form, and in the end it was a couple fields on a copy of a form - one was unassigned by mistake and one was possible from a previous table - but nonetheless it took me hours before Razzak got involved and took some time to help me. (thankfully) An error message would be a great present.....we shouldn't even be allowed to view the form because that saves the form first (I believe).
Bob c.
| "A. Razzak Memon"
<[EMAIL PROTECTED]>
Sent by: [email protected] 02/17/2005 07:31 PM
|
|
At 11:41 AM 2/17/2005, John Engwer wrote:
>... and sure enough I had a field unassigned. Last week I deleted
>a column from the driving table and I forgot to delete the field
>from the form that uses the table.
Also a very common mistake when copying and pasting controls from
one form (related to one table) to another form (related to another
table with different columns) is forgetting to assign the associated
fields for any controls such as DBEdits, DB ComboBox, and DB ListBox,
etc.
It would be really nice to include the -ERROR- message(s) related to
all controls with un-assigned data fields either when previewing the
form in Form Designer or at the Runtime, but allow the form to display
without generating an access violation, etc.
Well, maybe the "President's Birthday" or Future President's Birthday
will bring yet another fine-tuned version of R:BASE 7.1 (Update 80).
Yes, that's the ultimate satisfaction when you strive for perfection!
Very Best R:egards,
Razzak.
