Hi List,
We've deployed a solution with Microsoft SQL Server with SpatialWare, utilizing a
large number of mapped tables. All of these are
located in the main database (let's call it "A"), and they're all registered in
MAPINFO_MAPCATALOG in the same database.
However, we want to move all the tables to another database ("B"), but we've run into
a problem.
If we use the same DSN, which points to database "A", opening the tables in "B" will
return them unmapped. Registering the tables in
a MAPINFO_MAPCATALOG in database "B" doesn't work, since it's seems that MapInfo only
looks in the MapCatalog of the default
database.
We'd like to avoid setting up a seperate DSN for this, unless it's absolutely
necessary.
We've tried - in Pro - to use 'expert mode' to open the table using "B.dbo.tablename",
and it works with the correct rendition. But
if we then try to open the same table with the same MapCatalog registration in
MapX(treme), it balks saying that it can't find the
rendition column (MI_SYMBOLOGY). If we try to change the rendition column spec in
MapCatalog to a fully qualified refrence -
B.dbo.tablename.MI_SYMBOLOGY - Pro crashes miserably, and MapX just issues the same
error about not finding column MI_SYMBOLOGY.
Has anyone on the list tried something similar. And if gotten it to work, then how-to ?
Best regards/Med venlig hilsen
Lars V. Nielsen
GisPro, Denmark
http://www.gispro.dk/
http://www.gispro.biz/
---------------------------------------------------------------------
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Message number: 8931
