Hi Robert, Thanks for this explanation.
Another workaround could be to use DBMS instead of DAO. But of this is quite a different approach that sure will demand some recoding. Peter Horsbøll Møller GIS Developer Geographical Information & IT COWI A/S Rugårdsvej 55 DK-5000 Odense Denmark Tel +45 6313 5013 Direct +45 6313 5008 Mob +45 5156 1045 Fax +45 6313 5090 E-mail [EMAIL PROTECTED] http://www.cowi.dk > -----Original Message----- > From: Robert Crossley [mailto:[EMAIL PROTECTED] > Sent: Monday, November 17, 2003 10:50 PM > To: MapInfo List > Subject: Re: MI-L MapBasic and MS Access in the Mystery of > the Crashing Ap plication > > > Bill, Peter, > > I think the reason that mapInfo crashes or rebuilds the > indices is that it > is a workaround for a bug that has been in there for a few versions. > Since version 6.0? or at least when multiuser access to > Access tables was > allowed: If you have several tables in one Access database, > and some of > them had indices on them, and then you opened a couple of > them, made an > edit on one and then even did a selection on another, Mapinfo > would crash. > > The workaround given at the time was to destroy your indices > for all the > tables in the same database as the table your editing before > you edit and > rebuild them afterwards. This was of course pretty useless > if you needed > the indices to find the records to edit in less than a geological > timeframe. So for me the workaround was to create an array > of pending > edits while I had the indices intact, delete the indices, > apply the edits > and rebuild the indices. > > So anyway, a couple of years later, the workaround was embedded into > MapInfo as a "fix" and it seems to do it automatically. Less > GPFs, but > still a major performance problem. The problem still exists > sometimes as > it doesn't always fire off when your running a MapBasic > program. In my > current app, it has got so bad that I am now storing each table in a > separate Access database. Next step is back to Mapinfo native > tables. So > much for referential integrity and all that. If edits are being made > outside of Mapinfo, then I imagine the triggers to rebuild > indices are not > happening, so you get left with the GPF? > > Welcome to my nightmare. > > R > > On Mon, 17 Nov 2003 18:23:31 +0100, Peter Horsbøll Møller > <[EMAIL PROTECTED]> > wrote: > > > Hi Bill, > > > > One thing that has annoyed me when creating MB application opening > > Access tables thru DAO is that MapInfo sometimes recreates > the index > > on these tables. I have not been able to figure out when or why. In > > the beginning I thought it only occured when opening the > "tables", but > > this teory wasn't completely true. > > > > I have not been able to figure out the entire truth about > this issue, > > yet. > > > > Peter Horsbøll Møller > > GIS Developer > > Geographical Information & IT > > > > COWI A/S > > Rugårdsvej 55 > > DK-5000 Odense > > Denmark > > > > Tel +45 6313 5013 > > Direct +45 6313 5008 > > Mob +45 5156 1045 > > Fax +45 6313 5090 > > E-mail [EMAIL PROTECTED] > > http://www.cowi.dk > > > > > >> -----Original Message----- > >> From: Bill Thoen [mailto:[EMAIL PROTECTED] > >> Sent: Monday, November 17, 2003 5:20 PM > >> To: MapInfo-L > >> Subject: MI-L MapBasic and MS Access in the Mystery of the > Crashing > >> Application > >> > >> > >> I'm trying to debug a rather large MapBasic application that > >> mysteriously crashes sometimes (and takes MapInfo down with > >> it.) Evidence from numerous autopsies indicates that it dies in > >> different places, but sometimes it makes it through the region of > >> suspect code without a problem. It also works fine on some > machines. > >> > >> I've heard a rumor that using MS Access with MapBasic sometimes > >> causes problems like this, and this application does make > heavy use > >> of Access. Does anyone know of specific issues with MB and Access > >> that I should consider in tracking down this evil genius of a bug > >> before it strikes again? > >> > >> -- > >> - Bill Thoen > >> ------------------------------------------------------------ > >> GISnet, 1401 Walnut St., Suite C, Boulder, CO 80302 > >> tel: 303-786-9961, fax: 303-443-4856 > >> http://www.gisnet.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: 9172 > >> > >> > > > > > --------------------------------------------------------------------- > > List hosting provided by Directions Magazine | > www.directionsmag.com | > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > Message number: 9173 > > > > > > -- > > 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: 9179 > > --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 9188
