Man-wai Chang wrote on 2016-02-03:
Interesting reminder!
I didn't think much about the underlying mechanism, and was coding like a blind followers. The tutorials and books out there didn't talk much about that underlying "darkness" neither. :)
I guess the C5 errors had something to do with memory allocation, conflicts if not leaks?
On Tue, Feb 2, 2016 at 11:37 PM, Richard Kaye rkaye@invaluable.com
wrote:
Grids are tetchy critters and prone to blowing up with C5 errors,
especially if you
requery the datasource while its still associated with the object. In
general,
the tricks have been to temporarily reset it to nothing, rebuild your underlying datasource, and then reestablish the relationship to the
grid object.
Man-wai,
I would suspect the Dymanic properties that fire code to update specific controls within the grid may cause a C5 if the cursor is not carefully handled. The best way to prevent oddities is, either set the RecordSource to an empty string and back, or ZAP and INSERT/APPEND data back in to it.
Timers that fire, which then reference another object have been known to cause hard to reproduce errors, and a rare C5 for me.
Exiting out of code in the middle of a CATCH of the Try/Catch have caused a C5 for me.
Corrupt CDX files have caused a C5 for me.
ActiveX controls, those are my bane, with C5's. I can't reproduce them in house, but several customers get them.
Tracy Pearson PowerChurch Software