Hi guys, I am trying to build a tooltip that contains data from multiple tables (essentially - a join). I have a point layer that gets populated from an ODBC source. The table has a relatively simple structure: PointID, PointName, PointLat, PointLon and PointTypeID. Now this PointType is a foreign key into a Types table which contains only the TypeID and TypeName fields. What I'd like is the tooltip to resolve the PointTypeID and get the TypeName to display.
I tried feature-joining the ODBC Source with itself (figures since both the tables are in the same db), and created a new Extended class (named PlaceType). This extended class has its primary feature class as the Points table (or Default:points) and the secondary feature class as the Types table (Default:types). I then specified for join the PointTypeID column and the TypeID column. Now when I reselect the feature source (in an effort to update the Feature Class dropdown list) I DO get the Default:PlaceType class, but if I select it I lose all my geometry fields. This extended class apparently does not pick up the Lat and Lon columns from the original tables, it only picks up the PointID and PointName columns. So basically in an effort to get a join I lose my geometry fields. Any insights into this or would I have to add *yet* another layer with only tooltips and no points? Probably a better solution would be to allow SQL type expressions in the expression builder, a bit reminiscent of MG 6.x. Regards, uXuf -- View this message in context: http://www.nabble.com/Building-an-intelligent-tooltip-tf4840591s16610.html#a13849076 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
