I have an updatable view (made updatable through the use of an INSTEAD OF
trigger) which updates fine in Enterprise Manager save for the fact that I
had to get rid of primary key columns which in my case were IDENTITY ones:
rather than supplying an appropriate value for the field, SQL Server
complained about the presence of NULL in the column. Well, with or without
the primary-key column, the view is updatable (if I included the IDENTITY
column, I could supply any value which would do fine: next time I opened the
view, the value was replaced with the proper one in both columns - the view
consisted of two tables joined by that primary-key column which was IDENTITY
in one of them).
Now, unfortunately I have failed to make things work in an Access project.
Without primary-key fields the view is not updatable but with them Access
complains about the NULL in the IDENTITY column. Funnily enough, unlike
Enterprise Manager, Access does display 'AutoNumber' or something in the
IDENTITY column, it does show the next value when I start typing in the row,
yet when I try to save it, it complains about NULL in the column showing the
next available number.
Any ideas how this can be put right?