What exactly is the problem with the other software? If you want to keep on using this same Access database and its table with MapInfo then you need that field there, as I understand the way MI works. <plug> You could change to Manifold System, of course :) It has much better database handling facilities, without the need for a 'spatial database engine' or similar middleware. And, you can simultaneously edit the MS Access database that's GIS-connected, within Access, or run Access SQL from Manifold itself and return recordsets as desired. </plug>
IL Thomas GeoSciSoft - Perth, Australia > -----Original Message----- > From: Ellingham Morgan [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 17 November 2004 9:29 AM > To: [EMAIL PROTECTED] > Subject: MI-L MapInfo/Access backend indexing problems > > Hello, > > We have an MapInfo/Access back end that is causing an indexing problem > with a third party software. The problem is the 'auto generated' column > that MapInfo creates when you have an .aid back end. I can delete the > column/index in access but MapInfo keeps generating it whenever you open > the table in a GIS. > > > Morgan Ellingham > > GIS Technical Officer > > Level 1, 150 Jolimont Rd, East Melbourne > > Ph: (03) 9261 5065 > > Mob: 0419 145 666 > > Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > > --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 14080
