I have a complicated database that has many cross linkages in it. It is currently in Access and is linked to MapInfo TABs. I am considering moving the TABs and the attribute database into Spatialware for SQL Server to help maintain data integrity. My question is how to handle the separate database that has the attributes? I could make one instance of SQL Server for the database, and load the TABs via easyloader into a separate instance of SQL Server. BUT at that point I will have a spatial database and a separate attribute database. Has anyone ever tried linking the two databases together? Note that the attribute database is too complex to turn into a flat table of attributes. Any hints or suggestions are greatly appreciated.
Karl McElhanney Consulting Services Ltd. L100 - 780 Beatty Street 450 - 999 8th Ave SW Vancouver, BC Canada Calgary, AB Canada V6B 2M1 T2R 1J5 Tel (604) 683-8521 Tel (403) 612-8521 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
