Reg : Incorrect edit type -> unversioned feature class

[VikramS]

Hello all ,

I am trying to do start editing on a feature class in arcmap which is not versioned . I unchecked the option which is under editor toolbar --> Options -->Versioning (Edit a version of the database with the ability to undo and redo) .

I am getting an error Incorrect edit version type . I am using Arcmap 10.1 . SDE 9.3 and SQL Server 2005 .

What could be the reason?  Please help

[WilliamCraft]

Do you have a mixture of versioned and non-versioned feature classes in your map document by chance?  Alternatively, was there a feature class which participates in a topology or network that might have been registered as versioned initially but is not any longer?  If either of these scenarios apply, this error message has been known to appear in those cases.  The link below discusses these situations:

http://support.esri.com/en/knowledgebase/techarticles/detail/38414

If the first scenario I mentioned applies, then I would recommend trying to separate your versioned and non-versioned feature classes into two separate map documents for editing purposes.  Another option might be to use two different ArcSDE connection files... one for versioned data and another for non-versioned data.  In the Sources tab of ArcMap, you will see both connections listed... each with their own data listed underneath.  When you start editing, I believe ArcMap will present you with a choice of which data source to edit.  This may help to prevent the error from appearing if you are unable to separate your data into two map documents.

[VikramS]

Hello William,

Thanks for replying . I think the problem might be because the feature class which is unversioned is inside a dataset . I was checking other feature classes in it . It seems there is a mixture of versioned and non versioned feature class inside the dataset . So Arcmap thinks that the all feature classes inside the dataset are versioned . Correct me if I am wrong

Thanks once again.

[WilliamCraft]

That could certainly be the reason for the error, yes.  But, let me know if either of the two suggestions I mentioned prevents the error from occurring.  To re-cap, one suggestion was splitting versioned and unversioned feature classes into two map documents.  The other suggestion was using two ArcSDE connection files (one for versioned and another for unversioned) to path your layers in the map document and seeing if opening an edit session lets you pick one.