I'm migrating a very old platform from a SQL Server 2000 backend and MS Access 2003 as its frontend to SQL Server 2012 backend and MS Access 2010 as the frontend. This obviously means a bit of headache, but at the moment I'm stuck at a "limitation" of the new database.
Apparently (according to this: http://jagbarcelo.blogspot.se/2006/09/identity-columns-in-view-treated-as.html) any compatibility level above 80 in SQL Server will treat identities as ordinary ints in relational views. This creates problems in my frontend as no new records are created (exists in both 2003 and 2010 version of Access).
My question is: is there any way to fix this in the database (backend) rather than changing the whole frontend?
Update: I'm still curious about this so an update from further testing..
Apparently my above situation is the result of a view containing relational tables. In a compatibility level of 80 it exposed a natural identity column (is_identity = true), but for later compatibility levels no identity was exposed.
Can this be forced in some way, by some sort of annotation perhaps?