Hi I haven't come across your problem, as I keep all our field types standard. But I think it may be the same problem MI has supporting some types of fields from MS Access.
The following is an extract from the MI 6 help file. This is most likely true for SQL Server. # #Unsupported Fields In Access Tables # #A dBASE DBF or Microsoft Access table may contain fields that are not supported in MapInfo. #When you perform certain table maintenance operations on these tables, there will be a permanent loss of data for those fields in the DBF table or Access table that are not supported in MapInfo. #For example, MapInfo does not support the Memo field from DBF tables, or the Memo, OLE, Replication ID, and Hyperlink fields from Access tables. When you perform table maintenance operations on these tables, such as packing a table, MapInfo re-creates the native table with the structure of a MapInfo table. As a result, there will be a permanent loss of data for those fields in the DBF or Access table that are not supported in MapInfo. Cheers Ian Ian Tidy Network - Technical Assistant Marlborough Lines 1 Alfred Street, P.O. Box 144, Blenheim, New Zealand Phone + 64 (3) 577 7007, Fax + 64 (3) 577 7014 DDI Phone +64 (3) 579 3831, Mobile + 64 (27) 283 1862 mailto:[EMAIL PROTECTED] http://www.marlboroughlines.co.nz -----Original Message----- From: Feinberg, Harold [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 8 January 2002 11:04 a.m. To: MapInfo-L (E-mail) Subject: MI-L MI and SQL Server This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. Hi Listers, ODBC links can be very easy and seamless, but also very frustrating. I'm Trying to work out the problems a co-worker is having w/ a link from MI 6.0 to SQL Server (version ??). One problem is the table that is in SQL Server has numerous fields of text that don't display in the linked table browser. My first suspicion is that these are Memo or BLOB fields and thus can't be displayed in MI. I would love to hear from anyone who has worked out a solution to this problem. Additionally, can anyone share there experiences in implementing a server based ODBC link to MI from SQL Server (what are the pros and cons)? Should we ditch SQL Server and go w/ another Client server software? Harold R. Feinberg Research Analyst 1 GIS Ca. Dept. of Conservation: Division of Mines and Geology (916) 445-2673 _______________________________________________________________________ List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MapInfo-L" in the message body. WARNING: THIS MESSAGE HAS BEEN EXEMPT FROM CONTENT AND VIRUS CHECKING. PLEASE OPEN WITH CAUTION. CAUTION:This e-mail may contain attached file(s). This has been virus scanned, but care should be taken when opening any attachment(s). This e-mail is only intended to be read by the named recipient. It may contain information which is confidential or subject to legal privilege. If you are not the intended recipient you must delete this e-mail and you may not use any information contained in it. Legal privilege is not waived because you have read this e-mail. _______________________________________________________________________ List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MapInfo-L" in the message body.
