Most common is running with whileopt on and violating the rules of using whileopt. Trace does not optimize while-loops and so the problem does not show.
I've also experienced this once when the DB structure had become corrupt. Reloading and UnLoad all (then reload) both did not reveal a problem... but at one point I was using Bill Cook's suggestion of unloading the structure separately from the data, and _shizam_, there it was. Ben Petersen On 14 Feb 2002, at 0:08, MJS wrote: > Is there a list of reasons why an error might not show up using Trace, but would > show up using Run? It can be very frustrating when that happens! > > TIA! > > Mike Sinclair > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
