[AccessD] Resetting Autonumber seed

Or even better - Never use autonumber for meaningful keys like Order 
Numbers.   

Autonumber is a great tool for generating the *surrogate* primary key which 
you should always have in your tables (DARFC) - but it causes no end of 
trouble when you try to use it for real data. 

On 10 May 2006 at 11:58, MartyConnelly wrote:

> Or just use GUID's instead of sequential autonumbers although this might
> frighten auditors.
> 
> Gustav Brock wrote:
> 
> >Hi Robin
> >
> >Then read the highest order no. before deleting records, delete records,
> >compact, append one record (dummy order) with order no. set to the read
> >order no.; finally, delete this record. Now the next order created will
> >have the read order no. plus one.
> >
> >/gustav
> >
> >  
> >
> >>>>Robin at rolledgold.net 10-05-2006 20:04:27 >>>
> >>>>        
> >>>>
> >Gustav, Matt,
> >The problem is deleting Orders from one table and transferring to Posted
> >Table via queries- Database is compacted overnight which resets the seed to
> >the lowest order no left - this results in duplicate order numbers when
> >they are eventually transferred...
> >
-- 
Stuart