Well, this is interesting. I got it to work by going back to Version 1 tab
files. Another curious difference is that you must list the table with the
graphics SECOND in the join clause (COBoulder1.tab contains the map
objects in this case.) If you don't do this, the view will not have the
Street field indexed and the Find command will not work. But, if you do
this with Version 3, you will get no graphics. In Version 3, the graphics
table has to be listed first, but that messes up the indexing and so the
street names are all wrong.
However, by using version 1 tab files things actually work and I can now
use the built-in MapInfo geocoding feature with my new TIGER data. But I
would still like to know how to do this with the latest version of MapInfo
tab files because I would hate to see some new future version of MapInfo
suddenly refuse to work with my old tab files.
Below are the Version 1 tab files that work in MapInfo ver 7.8 (compare
with those listed in my previous message if you're interested.)
COBoulder.tab
-------------
!Table
!Version 100
Open Table "COBoulder1" Hide
Open Table "COBoulder2" Hide
Create View COBoulder As
Select Street,FromLeft,ToLeft,FromRight,ToRight,Class,TLID
>From COBoulder2, COBoulder1
Where COBoulder2.StreetId=COBoulder1.StreetId
COBoulder1.tab
--------------
!table
!version 100
FIELDS: 7
FromLeft Integer
ToLeft Integer
FromRight Integer
ToRight Integer
Class Char (3)
TLID Integer
StreetId Integer Index 1
COBoulder2.tab
--------------
!table
!version 100
FIELDS: 2
StreetId Integer Index 1
Street Char (40) Index 2
---------------------------------------------------------------------
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Message number: 17251
