Ed, I have dealt with UniData file corruption in the past and it can be quite difficult to get a handle on it. I have seen files get corrupted by memory failures, processor failures, and disk failures. If this is not due to a hardware issue a file can be corrupted,(or at least used to be corrupted depend on your release) by performing a unix copy (cp -rp) on a file that is being updated, and running guide against a file that me be in use. There could be more issues that haven't been listed.
I have also found that running guide against a corrupt file does not always fix the file. In some cases a second check against a file by guide has turned up more errors. There are times when a file has been corrupted, guide can't fix it. I usually make a copy of the file, clear it, and copy the records into it, and run guide against this file. The fact that AE will let you access a record only means the editor can read the record. If you try to change something in the record and file it, you will see errors. We don't use triggers, so I can't comment on that. Rich Richard Sammartino Systems Analyst School District of Philadelphia 440 N Broad Street Philadelphia, Pa 19130 Phone: (215) 400-5086 Fax: (215) 400-4411 ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
