AnsweredAssumed Answered

Saving edits when default version keeps changing.

Question asked by msbsmith on Jul 23, 2014

Hi,

 

When creating a new featureclass in my sde database I register it as versioned so that it can be edited.  So I now have lots of editable featureclasses in my database.

 

I'm getting in to an increasingly frustrating situation where a user can't save edits when they want because the default version has changed.  They have to try again and again to save until the save is accepted.  Similarly, if I need to load features from a shapefile for example into a featureclass in the database (using ArcCatalog), it can process the load and at the end pop up with a message saying the load didn't work because the default version has changed since I started.  This can be a pain if loading thousands of records because it can waste a lot of time looking like it's loading, only to fail at the end because the default version has change, I then have to start again.

 

I'm sure it can't be designed to work this way, so what is best practice here, how can I overcome this?

 

Thanks,

 

Mark.

Outcomes