Christophe,

Are you talking about linking to the Access table through ODBC or opening an Access table through Open Table (file of type = Access database). The second is what MapInfo uses the register command for.

I think that MapInfo uses a integer primary key to link to the map objects contained in outside the Access database in tablename.map. It haas always worked that way.

I'd imagine you can link to Access through ODBC because you can't have map objects associated (except points) and there is no need for the integer primary key - I may be wrong on this one - I don't have 7.8

r

On Fri, 28 Jan 2005 11:22:43 +0100, Christophe Brabant <[EMAIL PROTECTED]> wrote:

Well, after many tests, here are the results :

- MapInfo 7.8 Documentation says :
        "Registering Access Tables "
        "When you register an Access table, MI Pro checks for a counter
column with a unique index. If there is already a counter column, MI Pro
registers that colums in the .tab file. The column is read-only"
        "If the Access table doas not have a counter column, MI Pro modifies
the Access table by adding a column called MAPINFO_ID with the counter
datatype. Etc...."

So I don't understand why I have to add myself a NumAuto volumn into the
Access table. If i do not add it, I always get the message "The table must
contain an unique and NUMERIC key" etc...
This NumAuto column will have no usage, no importance for the database, but
in spite of what MI Documentation says, I have to add it.
However, contrary to what I said into my first message, the Primary Key CAN
BE a Text field.


Thank you

-----Message d'origine-----
De : Ian Hull [mailto:[EMAIL PROTECTED]
Envoy� : jeudi 27 janvier 2005 17:04
� : Christophe Brabant
Objet : RE : MI-L Querying ACCESS database with MapInfo 7.8



No, I have managed to link an Access table through ODBC with a single text
field that is defined as the primary key - i.e. indexed with no duplicates
(doubles). Null (empty) values are not allowed in this field.


Regards,

Ian Hull


Greater Manchester Transportation Unit Salisbury House Granby Row Manchester M1 7AH

Tel:      0161 455 2059
Fax:      0161 455 2071
E-mail:   [EMAIL PROTECTED]
Website:  http://www.agma.gov.uk/Units/TransportUnit.htm



                      "Christophe Brabant"

                      <[EMAIL PROTECTED]        To:       "'Ian Hull'"
<[EMAIL PROTECTED]>
                      ad.etca.fr>                  cc:

                                                   Subject:  RE : MI-L
Querying ACCESS database with MapInfo 7.8
                      27/01/2005 15:48







I don't speak very well english... you mean that you have had the same
problems, and you solved it by adding a NumAuto field ?

I don't use more than one field in the PK...

Christophe

-----Message d'origine-----
De : Ian Hull [mailto:[EMAIL PROTECTED]
Envoy� : jeudi 27 janvier 2005 15:38
� : Christophe Brabant
Objet : Re: MI-L Querying ACCESS database with MapInfo 7.8



Christophe,

I'm still using version 5.5 and had to jump through the same hoops. One
other think to look out for (in 5.5 at least) - the primary key (PK) had to
be a single field. In Access you can have more than one field as the PK - if
you use two or more and link it to MapInfo it seems to work but updates the
wrong records and is not nice.


Regards,

Ian Hull


Greater Manchester Transportation Unit Salisbury House Granby Row Manchester M1 7AH

Tel:      0161 455 2059
Fax:      0161 455 2071
E-mail:   [EMAIL PROTECTED]
Website:  http://www.agma.gov.uk/Units/TransportUnit.htm




"Christophe Brabant"

                      <[EMAIL PROTECTED]        To:
<[email protected]>
                      ad.etca.fr>                  cc:

Subject: MI-L Querying
ACCESS database with MapInfo 7.8
27/01/2005 14:16










Hi

It seems that even with Mapinfo/MapBasic 7.8, there is a limitation when
opening an access table through ODBC, if the primary key is Text field.
Mapinfo don't crash (I say that because Mapinfo 5 crashes), and says
something like that : "The table must contain an unique and NUMERIC key" (ie
Primary Key in Access language)


Does someone already have this problem, and how to solve it ?

(
the only solution I have found is :
- add a NumAuto field to the Access table
- set the primary key on this field
- set the property Indexed without 'doubled' (dont remember exactly what is
the word in english) on the Text field
)
but it's not really fine


 Thank you - Chris






**********************************************************************
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.


This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

Please contact [EMAIL PROTECTED] with any
queries
**********************************************************************






--------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 15039





-- ________________________________________________

Robert Crossley

Agtrix P/L
9 Short St
PO Box 63
New Brighton 2483
Far Southern Queensland
AUSTRALIA

153.549004 E 28.517344 S

P: 02 6680 1309
F: 02 6680 5214
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: 15048



Reply via email to