Dear Karl
If Users are updating Access tables using Access and not via MapInfo
then MapInfo has to keep building its AID file. If they are familiar
with Visual Basic their best bet is to open the Access tables in VB and
use integrated mapping to control MapInfo.
This is probably not what you wanted to hear, but the way MapInfo opens
a single table within an MDB file and exclusively locks it limits you
anyway, and the fact that other users change the dbf ( why are you using
dbf and not mdb by the way?) means rebuilding of indexes.
Hope this helps.
Regards
Bob
In message <[EMAIL PROTECTED]>, Terratech Mapping Services
Inc. <[EMAIL PROTECTED]> writes
>Hi,
>
>I have a client that has phoned me up and asked about a problem they are
>having. They have Microsoft Office 97 and are using Access from it with
>MapInfo Professional v5.0. Their copy of Access is located on a network
>so more than one person can work on the database. They are having two
>problems. One is that their client point data is getting out of sync
>with their MapInfo table. I think this maybe caused by deleting records
>in Access which causes a renumbering of records? The other problem is
>that they claim the .dbf file which is created by Access is deleted on
>random occasions and they have to recreate their MapInfo table, and go
>through the entire geocoding process over again.
>
>They upgraded to MapInfo Pro v5.5 and the problem still exists. I
>suggested that they check for any patches to Access on the MapInfo
>website, thinking that it could be an Access problem. Anybody else have
>any suggestions?
>
>Cheers,
>Karl
--
Bob Young
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
