Okay, SQL Server inserts should work now if you use the SQL Server provider from the FDO 3.7 final release.
But transaction rollback is still broken if you do MgFeatureService::UpdateFeatures with useTransaction = true and an exception happens in post-insert processing. This is where the old SQL Server provider blew up and left you with an internally dangling transaction that cannot be accessed. If you require transactions, try using the overload of UpdateFeatures that takes a MgTransaction instead. If any exceptions are thrown in post-insert processing (shouldn't happen after 2.4, but just in case), the transaction object is still available for you to manually roll back. - Jackie -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Error-on-insert-features-into-SQL-Server-Spatial-tp4987600p5015080.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
