Mike, I think you have to consider that the implications of the corruption may extend beyond the obvious.
How about restoring a recent backup to "work table A", then repairing the corrupted table into "work table B", and then comparing A and B to produce a report of changes made to the data since the backup was taken. If all is good, B replaces production table, otherwise you'll have to deal with differences next, or go with the restored backup. Also consider using 'audit trails' for changes made to production tables, in addition to regular backups. This gives you another resource to use in database recovery. Bill > VFP9SP1 > > We've got a scenario where a 3rd party has polluted our memo fields, and > I'd like to write a cleanup that takes the value of the memo field and > does a STRTRAN to get rid of garbage. Straight forward enough, right? > No, VFP is throwing an error saying "String is too long to fit." So I > check the VFP system capacities and sure enough, that's the magic number > (16777184). > > What would you advise for Plan B in this case? The memo is basically > polluted with bazillion quote marks. I tried this but it fails with the > same message: > > REPLACE comments with STRTRAN(comments,replicate(['],1000),[]) all in > MyTable > > > Suggestions? tia! > --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.
