Dear All,

I would like to know why I have a field used for look-up based on realtionship, when the record is deleted, the field related still got the the content of the original, the field is supposed to get 0 or blank.

When the record is deleted, the look-up field can not get the data? is that right? ...but in my case it still gets the content even I used relook-up script?

Anybody know why?

Thanks

Anh Tran

The way relookup works, it will hunt for a related record to update the field. If it can't find one, it leaves the field untouched. Once the field has data, whether from a relookup or manually entered, that data will stay there until a new related field to relookup comes along, or you manually alter it.

If you need the field to clear itself if the related record is deleted, then you'd need to make it a calculation field, or script the clearing process.

Steve Brown

Better yet, don't have any field at all in the parent database, just display the related record.

Dear Bobweaver what do you mean by , just display related record?

Thanks

He means, do not use another field with a lookup. If you always want what the orginal parent value is, then simply always use the parent field.

Example

Database A , Field1

Dabasee B , Lookup of Field 1

If you want Field1 in Database B, Simply reference Field1 through the relationship that connects Database B to Database A. (Instead of a field that actually exists in Database B that is looking up the value of Field1 from Database A)

*********************************

On one of the other topics, if you DO want to use a lookup, it's possible to have it enter "blank" data if no match is found. In the Lookup options dialog box under "If no match then, :" select the 4th option (last one) and leave it blank. If no match is found during a relookup, it will enter this blank value. You also need to uncheck the "Do not copy contents if empty" to overwrite data if the orginal source still exists, but the field contents were deleted.