Karl Larsson 10.Feb.12 07:02 PM a Web browser LEILEI - 8.0Windows
I'm using LEI to virtualize documents that already exist on the SQL side, but which can be updated on the Notes side. The virtualization works fine, but updates fail.
As far as I can tell*, it's because SQL is using an Identity Column to generate a sequential key, so when Notes passes that same (unchanged) ID back as part of an update request, SQL chokes, because you can't update an Identity Column.
I guess what I need is for LEI to not try and do anything with the primary key - just leave it alone, and only pass back the fields that have changed.
I've seen other people complain about this issue on the forum, but no solution.
Any advice?
Thanks,
Karl
*LEI has got to be the most frustrating, irritating piece of software I've ever used. It has so much potential, but the debugging is appalling, there's non-existent online support and it flakes out at the slightest issue. I've wasted so much time on this already, and still haven't managed to use it on a live project.
Return to top
Identity Columns in SQL (Karl Larsson 10.Feb.12)
. . 
Print this page
