Are you using 2.4 RC1? You've encountered a classic bug with UpdateFeatures that has been fixed for this release:
http://trac.osgeo.org/mapguide/ticket/649 "Fixed" in the sense that such errors are now properly logged in Error.log and that the API documentation has been updated to indicate if MgPropertyCollection contains MgStringProperty instances, it means an exception was thrown for the matching command in the MgFeatureCommandCollection that was passed to UpdateFeatures. You should probably check if the Identity Property for that Feature Class is actually auto-generated to make sure nothing has been lost in DB -> FDO schema translation. - Jackie -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Error-on-insert-features-into-SQL-Server-Spatial-tp4987600p4987607.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
