Thanks, for looking.
The last thing prior is a very simple INSERT INTO.
I used to use the @@select identity with Access which worked fine, but up-scaling to SQL Server now.
I've checked the table and it does have a valid Identity column.
Using the following connection string:
"Driver={SQL Server};Server=(local);Database=MAS-Settings;Uid=X;Pwd=X;"
My best guess is the up scale wizard has screwed something up,