Malcolm Greene wrote: > Mike, > > I would scan through your original table, exporting out its contents to > another table. > > Perform your export by inserting a blank row in the export destination > table and then loop through all the fields in your source record, doing > a field by field replace. AFIELDS() will give you a list of fields to > loop through. > > Place your field by field replace code in a TRY/CATCH block and log any > field updates that fail by primary key or record number, field name, and > error message. > > Review your error log and go back and manually update any field updates > that failed. If you have a small number of errors you can do this with a > simple BROWSE command. > > Good luck! > Malcolm
Hi Mal, No, I wanted to create a simple, deployable tool for our support guys to use rather than passing the ticket up to Level 4 (us). That way, they just run the quick utility and voila....done. --Michael _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
