Good idea Chris, however, we are looking for a file format solution instead
of a process like ODBC since this is going to be deployed to many customers.
-----Original Message-----
From: PERRY Chris [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 08, 1999 4:28 PM
To: 'Perry, Mike'
Subject: RE: Map X vs. MI Pro compatibility
Mike,
What about using a DBase driver (ADO or ODBC?) to access the Dat file and
then read from that, or transfer to a text file.
Hope this helps,
Chris Perry
Systems Development CoOrdinator
Parks Victoria
Melbourne, Australia
Ph: 61 3 9816 6800
Fax: 61 3 9816 9876
[EMAIL PROTECTED]
-----Original Message-----
From: Perry, Mike [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 9 November 1999 4:41
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Subject: Map X vs. MI Pro compatibility
Importance: High
We are looking for a table/layer format in which the same instance of the
table/layer is 100% compatible in both MI Pro and Map X, and is accessable
by multiple users at the same time.
--Native files for MI Pro have a limitation in Map X in that a visual basic
grid control becomes prohibitively slow (nearly impossible to "browse"
tables in VB/Map X: e.g. a table of only 1,000 records can take > 1 minute
for a grid to appear).
--Microsoft Access tables avoid this limitation, but have a limitation of
their own: Page 359 of the MI 5.5 users guide states, "It isn't possible to
have multiple instances of MI opening the same Access table."
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [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]
