I am having trouble with doing object edits through a MapBasic progam in a spatial table that has its data in Access. THe table has indices.
The Application error was:
The instruction at "0xx0067b913" referenced memory at "0x03ffd000". The memory could not be "written"
- and then one that says the memory could not be read.
Once today I was able to trap the error referencing a line where a selection was made to a different table stored in the same access database after the object editing had been done. As I recall, this seemed to be the trigger point for a bug that has been around since version 6.0, ie, outstanding edits in one indexed table, and selecting from another table in the same Access database.
THe workaround that I had to introduce in another application was to drop all indices before making edits and reconstruct them after. This is totally impractical in this application.
I am about to experiment with putting the MI tables into separate Access databases (one per database). Can anyone give an update on the status of the actual trigger for this fault? Or even better, a fix or workaround that does not involve deleting and rebuilding indices each time?
R --
Robert Crossley
Agtrix P/L 9 Short St New Brighton 2483 Far Southern Queensland AUSTRALIA
153.549004 E 28.517344 S
P: 02 6680 1309 F: New Connection M: 0419 718 642 E: [EMAIL PROTECTED] W: www.agtrix.com W: www.wotzhere.com
--------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 8998
