[Using Access 95, Jet 3.0]

I developed a muilt-user app in  Access 2/Jet 2.5 and converted up to '95
(Not my choice !!) and Jet 3.0.

I started getting a duplicate value in index error when adding new records
via an rs.AddNew ... rs.Update. The trouble is the primary key is an
Autonumber (Increment) field and there are no other indexes in the table.

I implemented explicit transactions as per the on-line help as I thought it
would be something to do with the cacheing of implicit transactions but
though it may have reduced the number of times this occurs, it certainly
hasn't got rid of it.

I've read a long thread about problems with duplicates in primary keys and
autonumber fields but am unsure of the latest status of the issue. Can
anyone update me please.

Also with regard workarounds, what's the best way
1. Take control of the autonumbering away from Access and do it myself
2. Change the rs.Addnew... rs.UPDATE to a parameter query (I think this is
my preferred change at the moment - but don't know for sure whether this
will get round the problem)
3. Downgrade to Jet2.X
4. Any other option (Access 95 is a given, unfortunately and upsizing to SQL
Server is not an option)

Many thanks

Simon