Hi Jody,
Try opening the table using the 'manual' Open ODBC Table menu option. Save
the table, open the .tab in a text editor and look for any differences
between the syntax in this and that in your MapBasic statement. This may
give you a clue?
Hope this helps,
Pete, Ordnance Survey, UK
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 29 July 1999 14:05
To: [EMAIL PROTECTED]
Subject: MI Invalid Column Name error using ODBC
Using MapInfo Pro 5.0, I could execute the MapBasic statement:
SERVER i LINK TABLE "select REAL_SMA_CODE, OBJECT from HAIL_DETAIL" INTO
hail_detail File "c:\test"
where "i" is my ODBC link to an Oracle database.
The table HAIL_DETAIL has been cataloged, so it is mappable within MapInfo.
This works fine in MapInfo 5.0.
When I upgraded to MapInfo 5.5, I now get the Oracle error: Invalid Column
Name.
If I remove the OBJECT field from the above query, it works. But it isn't
mappable then.
Yet, if I open the table using the "Open ODBC table" from the File menu in
MapInfo, the query works (selecting the OBJECT field from the list of fields
displayed for the table).
Has the OBJECT field changed in different version of MapInfo?
Any help is appreciated.
--
Jody Cairns
[EMAIL PROTECTED], or
[EMAIL PROTECTED]
--
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
***
* This email/attachment(s) has been virus checked at OS *
*and is free of all known viruses.
*
* All non work related emails/attachments should be deleted
*to comply with 'Internet code of practice'
* as per office notice 524/98.
*
***
--
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
