There is a globalid type field that is required for database replication. This adds very robust support for field operations. however with the limited capability I have and the limited test environment arcmap/autocad map/mapguide 6.5, I can only provide information about what I have seen and experienced. In Map 2009 (fdo 3.3 I think ships with) out of the box, I can go right up to the point of checking in. at which point I get an error null value not allowed. I then experience problems removing the incomplete object from the edit set. After removing the global id field and adding a new feature (while still recieving the message of the edit set not being empty) I am able to check in the new feature and it seems to fix the incomplete feature. Not sure this is true.
possibly info for a diffferent track but geodatabase domainns do not enforced and are not discoverable.
