Regarding error 3262 - have a description:
runtime error 3262 couldn't lock table

So don't believe virus. Since I didn't lock from code, found error description odd other than
Access must put a lock on the table when double_clicking it (the table) for viewing, which causes
the Vb5/6 OpenRecordset call to error . Access must (doublclick table) consider this "design view"
-- as you point out -- even though I did not select or enter design from the Access menu.

The above said, SQL INSERT INTO should also fail since manual viewing locks the table.

I know I should upgrade this App to ADO, but like all things time and priorities.
For that matter "Classic VB" is out of date (per M$), but I love it as it does what I want.
This goes back to the old debate of which language should you use. If M$ had their way
you would be using a new language every six months.