No support for locking features in IM SQL Server

[jlgmccall]

Apparently there is no way to check out/check in features in a SQL Server Industrial Model. Apparently these commands are active but in fact do not work.

Here is simple scenario illustrating the problem:

-          Open MAP, connect to IM etc.

-          Select a feature

-          Check it out, Edit (say move it)

-          In DM verify it’s checked out via “Select checked out features…”

-          Open another MAP session
       Result: The feature was updated. Therefore it seems Map3D IM works in Direct Mode update always and the check-out is bogus.

Is this a known issue? Is there an workaround? Needless to say locking is a critical feature.

Thanks in advance.

[hence_the_name]

Hi,

there are two features related to Checkin/Checkout and writing back modified data immediately.

(1) Checkin/Checkout - means that you need to check out a feature before you can modify it. But as far as I understand it doesn't mean that any modification is not written back to the database. "Checkout" prevents the user to modify a feature accidently.

(2) Automatic Update - as soon as a feature is modified the change is written back to the database. Not matter if you enable "Automatic checkout" or not.

At least that is my understanding of it. I just wanted to give it a try (on oracle) but when you wnat to disable "Automatic Update" you need to assign a "Template". That is going to far for a quick test....

Rob

Map 2013 Help:

When Automatic Update is off (the default)[it's "on" by default here with our installation, Rob], your changes remain local until you check them in.

If you turn on Automatic Update, AutoCAD Map 3D immediately attempts to save any edits you have made to checked-out features back to the feature source. If updating fails for any reason, the setting remains off. You can reverse the changes you made (so your version matches the one that is checked in), or check out the drawing, re-enter your edits and then check it in.

[NateMoore]

From what little I know about industry models, you may be running into one of the SQL/Oracle differences.  If you look here, it mentions that " The jobs (long transactions) functionality is only available in Oracle given that it is based on the Virtual Private Database technology."

[hence_the_name]

Hi Nate,

in my quick example I didn't use jobs. Jobs is a beast of its own - I would say that using jobs or not - there is no relationship to CheckIn/CheckOut and AutoUpdate (but it's only an educated guess).

Greetings from Winterthur,

Rob