Jim I use the PROPERTY command. For example, I have a quote form where the csr can enter the customer number if the customer exists and the property command will fill in the the customer's info. If there is no customer number and we don't want to add one yet, then using variables the way we did in 6.5 would cause the fields to return to nulls. So, I give all the DBEdits component ids and on exit from the customer number field:
PROPERTY custname TEXTVALUE .vcustname PROPERTY address1 TEXTVALUE .vaddress1 PROPERTY address2 TEXTVALUE .vaddress2 PROPERTY city TEXTVALUE .vcity PROPERTY state TEXTVALUE .vstate PROPERTY zipcode TEXTVALUE .vzipcode PROPERTY payterm TEXTVALUE .vpayterm RETURN (the variables are defined in the variable list of the form: ie vcustame = custname in custlist whe custno=custno) Dawn -----Original Message----- From: Jim Buddemeyer [mailto:[EMAIL PROTECTED] Sent: Thursday, December 02, 2004 9:44 AM To: RBG7-L Mailing List Subject: [RBG7-L] - Alter lookup data In the "Easier days" of R:base (6.5 and earlier), there were two check box options on the forms for field settings; 1. User can change data in the field 2. Restrict the changes to the current table. This was nice when you used lookups for fields driven off an ID number but wanted to alter the data. For example if the default address needed to be changed for just one order the information could be altered and the record could be saved. The default information would only reappear if the ID number was modified. When I use the DB Edit fields and defined variables to populate the fields they return to the default values when leaving the field. Is there a way to achieve similar results in 7.1? Jim Buddemeyer
