Here's a workaround you can try: Create a second feature source (B) with the same connection parameters as feature source (A)
Create an extended feature class in either Feature Source A or B that joins to the same table from the *other* feature source. This way the optimization check that MapGuide does (does both sides of the join originate from the same feature source?) will fail and the default Feature Join behaviour is used instead of the buggy RFC123 behaviour. - Jackie -- View this message in context: http://osgeo-org.1560.n6.nabble.com/mapguide-2-4-sql-server-spatial-feature-source-can-t-select-the-data-store-and-can-t-use-join-extenss-tp5033688p5039894.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
