|
Hi Listers,
I've been having problems with commits to Access
from MapInfo 5.5 and wondered if you might be able to shed any light on
them...
I've (well, the client has) got this Access
database which is being geocoded in MapInfo. The problem seems to be that they
have a concatenated primary key in the Access table (two columns both designated
as primary key). One column is a unique integer, but the other primary key
column is a year value - in other words it's the same for all of a year's
records. I can open the table via ODBC and geocode it in MapInfo fine, but when
I commit the changes all the records get overwritten by the values for the first
record.
If I mess about with the table in Access and set
just one column as the primary key then the commit works OK, but I won't be able
to get away with this when they give me data for more than one
year.
Any idea if this is a feature, a bug or if I've
just screwed up and I'm using the wrong ODBC set up? I've looked through the 5.5
bug list on the MapInfo web site, but no joy.
All suggestions gratefully
received,
Nick Hall.
GIS
Consultant ________________________________________________________
WARNING - THIS E-MAIL TRANSMISSION IS CONFIDENTIAL. This e-mail transmission (including any accompanying attachments) contains confidential information which is intended for the named addressee only. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution or reproduction of this e-mail is prohibited. If you have received this e-mail in error please contact us immediately at [EMAIL PROTECTED]. Thank you. _________________________________________________________ |
