MartyConnelly
martyconnelly at shaw.ca
Wed May 10 13:58:18 CDT 2006
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... > >Thanks for your help so far - must leave this for tonight...!! > >Will return to it tomorrow > >Rgds >Robin > > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock >Sent: 10 May 2006 19:02 >To: accessd at databaseadvisors.com >Subject: Re: [AccessD] Resetting Autonumber seed > > >Hi Robin > >No, the Counter syntax works in Access 2000+. > >But why at all trouble with resetting of Autonumber? It's generally a >very bad idea. > > > > -- Marty Connelly Victoria, B.C. Canada