Dear Jim -
Well, I actually thought of the CURVAL() and OLDVAL() thing, but didn't mention it here...

I'm hitting this trigger when the user Saves the screen form, whose data environment for the table being edited is set to Optimistic row buffering. If I suspend during my routine, here's what I see:

CURVAL(field) = old value
OLDVAL(field) = old value
table.field = new field

Is this the usual scenario? Haven't done a lot with buffering, as I've been in the SBT/ACCPAC backwater for a long time. I think this has to do with the values being used on the screen are in some kind of mid-state and haven't been written anywhere, Is this right?

The problem is I want to SELECT the record out to a file and copy it to an ASCII format. Again, if I SCATTER the values beforehand and use the memvars instead of the table values, it works.

There's GOT to be a way to do this without using memvars, isn't there?

Thanks in advance! (I know this is like teaching VFP kindergarten, but I really appreciate it!)

-- John

>John,
>
>Read up on CurVal() and OldVal() in the help file. Your answer lies in those functions.
>
>Also remember that your trigger can stop the save so be sure you have accounted for that before you make your text file.