You are doing what is essentially a "backdoor" approach that causes some parts of the system (ie. the MapGuide Server) to not be aware of such changes. This is why you should do things through the abstractions provided to you and not try to take shortcuts like this.
In this case, you would describe the schema of your Feature Source (MgFeatureService.DescribeSchema()), find the MgClassDefinition that maps to your database table, add/modify/delete the relevant properties in this class definition and then apply the schema back into the feature source (MgFeatureService.ApplySchema()) so that the structural changes can be applied. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/C-Dynamically-Adding-New-Fields-To-Existing-Layer-tp5092346p5092350.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
