I thought that a newer version went into Wonder, but I could be wrong.
Without the plugin, I am getting the following error message when I attempt to insert a record from a form: "Cannot insert explicit values for identity column in table 'RxUser' when IDENTITY_INSERT is set to OFF." When I went into the EOModel to check
things out, I noticed the plugin was not set for the current model. That led me to looking for the MicrosoftPlugIn.framework.
Identity columns and EOF don’t play well. The database expected to populate the identity column when the row is committed and EOF needs to know the PK value before it commits. I have never used nor know anything about setting IDENTITY_INSERT to off.
I could possibly work. The plugin above does not do this.
Any suggestions for working with SQL Server in general would be appreciated. Coming from FrontBase, SQL Server seems like a 2-ton gorilla trying to lift a breadbox.
It is not my favourite database. My two pieces of advice are: don’t use identity columns and don’t lock on timestamp columns as SQL Server’s timestamps are less accurate than JDBC/EOF and this results in optimistic locking failures. Or did with the 2008
version.