Larry,
Does your client want unique IDs?
If they always want unique ID, then once a ID is assigned, it can't be
re-use.
Unique ID will also allow data to be stored in other table related to the
specific ID, however if the ID where to be re-used, then you may have a
security issue where people or seeing other peoples data, of course this all
depends on the type of data being stored, etc.
To clear the database, you must delete all records in the table, then Tools
| Database | Compact and Repair will then reset the counter to 1. If there
is a record, then the count will not be re-set.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
"Larry Rekow" <larry@netgeexdotcom> wrote in message
news:(E-Mail Removed)...
> On Sat, 24 Jan 2004 16:55:45 -0500, "Thomas A. Rowe" <(E-Mail Removed)>
> wrote:
>
> >File should read Field
> +++++++++++++++++++++++++++++++
> Many thanks for your response.
>
> My first instinct was to use an auto number id...however....when i
> first tried this....i create several "test" records to make sure it
> worked. then when i was satisfied it worked, i went back and deleted
> these records. but to my chagrin, the 'real' records created after
> this did continue the sequence. deleted id numbers were not replaced.
> any way around this behavior?? also, if someone were to make a new
> record and want to delete it for whatever reason, the id can never be
> used again. the people i'm developing this app for don't want holes
> in their numbering sequence.
>
> oh, also, i'm using Access as the d/b
>
> thanks.
>
> L
>
> - - - - - - - - - - - - - - - - - -
> "Forget it, Jake. It's Chinatown."