My main application is exactly what you describe - a mapinfo program that the data is stored in a set of tables in an Access database. There are two main issues that I know of.
There were major problems where you had multiple tables in Access if you edited more than one table, and those tables had indices on them. MapInfo would crash, particular if more than one user was using them. You used to be able to get over the problem by closing all the tables and taking the indices off them before editing them. Now MI triggers an index rebuild, which is fine, but if the table does not have the index as part of its structure, eg. if the index is triggered by a creation of thematic map, MI will still crash. I still haven't quite defined all the requirements to make it happen, but just recently had a situation where I was getting a lot of GPFs after creating a thematic map on a temporary column based on another access table using a common field to link them. MI used to create an index, but then crash. When I indexed that column in its table structure, the crashes stopped. Another quirky one is if you add a record to a data table from access, and then do a selection from mapinfo that should return that record.... it doesn't. You can see the record in the browser even. Reopen the Access table from MapInfo (not the tab), or edit and save a record from MapInfo, and run the same query and it will find that record. Quite a hoot for phone support. (Yes can you see the record in the database? OK did you type the key index correctly? Of course I believe you." probably related to MapInfos record referencing, but quite a challenge if you want to have a system that allows editing from either Access or mapinfo. I shudder to think of the potential issues of having an integrted mapping program that used this type of data structure, and have not gone down that path because of it. At least MapInfo is one step ahead of ArcView which doesn't allow multi user access to access tables (on last check). Mi has since 5.5. Mind you ArcViews concept of storing the shape object stored in an OLE field in the Access database is streets ahead of MapInfo's data structure. Have you considered a SQL database instead? Good Luck R 24/03/2003 15:38:02, "APR - Greg Mules" <[EMAIL PROTECTED]> wrote: >I am advising a client to go with the "live" link MapInfo / MSAccess in >which MSAccess tables are generated from MapInfo and the text data is stored >in Access. We want to extensively use MSAccess to manage, filter, query, >report on the data generated by MapInfo and combined with many table >generated in MSAccess > >Can someone tell me the limitations (or point to a discussion site) of >working with tables in Access that have been generated in MapInfo... I >understand the Memo and OLE field limitations and there is some issue with >MSAccess security (more info here please)... BUT has anyone had any other >issues with using MapInfo generated Access files in a full MSAccess >application > >Thanks > >Greg Mules >APR Geo Information Services >PO Box 59 >GREENSLOPES Q 4120 >Australia >Ph +61 7 3394 1366 >Fax +61 7 3394 1355 >Mob 0438708361 >[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: 6059 > > Robert Crossley Neo Software 9 Short St New Brighton 2483 Far Southern Queensland AUSTRALIA P: 02 6680 1309 F: New Connection M: 0419 718 642 E: [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: 6061
