I have now convinced myself that the rogue ID problem is SQL Server not
Access (I reproduced the behaviour in Enterprise Manager), so I won't
pursue it on the newsgroup. I'll pick it up at
microsoft.public.sqlserver.