Jeff or others,
We're using the latest version of Map SS3 and Access through ODBC on Windows 7 and we're experiencing some unexpected/undesirable bahaviour with (as an example) Group Holes. NB. It may also be happening with other element types too but this was the example we first came across.
If we have a Group Hole which is an Inferred Feature and it's dropped the record is not removed from the database. If however the group hole is a Native Feature, Map seems to have the intelligence NOT to be able to drop the feature. The preferred behaviour would be that if we dropped the Group Hole of an Inferred Feature, all associated records were also removed from the database. It may well be the case that we have a Group Hole Feature that we want to drop and edit/modify and then promote it back as a new feature. The way it currently seems to works is we're left with orphan records in the database.
We were beginning to think it would be 'safer' to have all our information as Native Features as opposed to Inferred Features when we noticed the next problem.
If we use standard Microstation and reference a Map file which is made up of Native Features, Microstation won't let us copy the elements into the file. This is undesirable. A preferred options would be to allow it to copy the elements but strip the attributes off. Perhaps there's a switch somewhere that allows this but if so we weren't able to locate it.
Another problem is if while in Map we Drop a Complex Element but then 'Undo' the drop, the original record(which may have contained a variety of attribute information) is deleted and replaced with a new blank record. The more desirable response to undoing a drop would be for the original record to be reinstated........not just the original feature graphics.
Every now and again when we do a cross check between our Map Graphics file and the assocated Database we invariably find we have orphan records appearing. The above is probably a reason for some of these. We should be able to use the information in the database directly to do certain queries if so desired however ophan records cause obvious problems here.
Could you please comment on and advise.
Any feedback?