Sadly, your version of SQL Server (2005) is not spatially aware. But if it was (like SQL Server 2008 and newer), you would have both the spatial and non-spatial data residing inside the same database and using views to encapsulate a join of these two tables. The view itself can be recognised as a Feature Class in MapGuide allowing you to create a layer off of this view and creating styles and themes off of the joined data. Through triggers or regular update routines, you can keep the underlying tables in this join refreshed with the latest data.
Do you have the choice of upgrading your SQL Server or using an alternate relational database? - Jackie -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/FDO-Toolbox-Connection-tp6410463p6410943.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
