SHEESH!! The below WORKS!! In fact it HAS been, however, I've got a copy of the data on a network drive(being used by my beta testers), and a copy on my local drive....for some reason when I'm testing my program it references the NETWORK data, while I'm working with the LOCAL data....ARGH!!! Weird stuff!! Anyhoo, thanks for your help:)


>>I guess, your only option (if you really want to autonmate it) is to write your own UPDATE trigger which may search through the child tables, recalling some records there. This way you probably will flag this trigger procedure to prevent unwanted 'recall' cascading.
>
>Well, here's an update...I've put in some extra code that will invoke the recall on the child table itself, here's the whole bit:
>
>IF DELETED()
>RECALL
>thisform.refresh()
>IF "SSU"$LCALIAS &&tests to see if we're in the table that's a parent table
>SELECT CMSER
>RECALL FOR CMSER.SBSERNUM=ALLTRIM(LCVAL)
>SELECT &LCALIAS
>ENDIF
>
>Explaination of above, I have 3 tables I'm working with, when I'm accessing the parent(SSU), which is stored in LCALIAS, I select the child table, then LCVAL is holding the value of the Serial # that was recalled in the parent table. All this ONLY takes place if the record that I seek for is DELETED.
>
>The above works, but not without failing a trigger, I'm not sure why...because the ser# is recalled in the parent first, so I'm not trying to add(insert?) something to the child that's not in the parent...Anyone have any clues????