Auto number
Paul
because of problem but when I do this I loose my auto-number ref, how
can I get around this (some records have been deleted therefore can nt
just recreate it.
Salad
Could you define your problem? Your description is confusing. Guessing
at your issue....
You could create a new table with the same fields as the source table
and add a new field; OldID, type Long. Then create an append query and
store the autonumber value in the OldId column.
Or Copy/Paste the table and call the Source table something like SourceCopy.
Or CTOL+C/V the source table and save the structure not data and run an
Append query.
Chuck Grimsby
Personally, I gave up on Autonumbers a long time ago. There are just
too many reasons (at least in my mind) not to use them! It's just too
darn easy and fast to "roll our own" if you need something like that.
I don't mind counters in SQL Server, but not in Access (though I do
tend to avoid them in SQL Server as well, mostly out of habit).
If your autonumbers *really* need to be unique (and survive deleted
records, etc.) don't allow deletes from the table. Just mark them as
deleted somehow instead (I tend to use a date/time column marking the
date/time the record was deleted).
hbinc
Hi Chuck,
I have another way of working, in which I use Autonumbers in every
table. But, the value of the Autonumber has absolutely no meaning. It
is only used to identify THAT SPECIFIC UNIQUE RECORD.
As soon as I need a range of numbers that must be continuous, I use a
separate field to contain that number.
By using an Autonumber for every record (with an ID-name derived from
the table), I can generalize on working with records. This means that
whatever the application is, or the relation within an application, I
can work in the same way. Result is that the creation of new
applications or changing of existing ones in term of Forms, is
completely automated.
I like the meaningless Autonumbers!
HBInc.