The problem with most C0000005 errors seems to be the inability to duplicate them. We had quite a number of puzzlers, most of which went away once SP3 was installed.
Now I've got one that appears to be related to the SCATTER NAME. I wish I could boil the code down to something postable. What the app does is take a text file and converts it into a VFP table, which after more processing gets imported into SQL Server (via SQLEXEC() calls). Works fine up thru the first 1351 records. But somewhere after that, things get screwy. Doing a simple "SCATTER NAME oName" and then doing something with the new object (in this instance testing EMPTY(oName.Fieldx), or especially an EVAL() ) will blow it out of the water. Almost as if the workstation has run out of memory. Or maybe it's just running out of tolerance.
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
