You may need to cut down the intake of caffeine and/or other
stimulants.
A simpler solution to the threat of users changing things in the
tables is to change the form properties to data entry only. That way
they can enter new information but not go back and alter information
already in the table. Unless they are clever enough to open the
tables directly.
Doing that will make it unnecessary to go through the steps you now
do.
Once you have things down to a single table for the operation see if
the autonumber issues might not have gone away. If not, post back.
HTH
--
-Larry-
--
"WMorsberger" <(E-Mail Removed)> wrote in message
news:07A875DC-AE1D-435B-906A-(E-Mail Removed)...
> Ok, so here is my situation - I have a form that is currently
associated with
> History table - the reason that I call it a history table is because
it
> doesn't hold the information, I have a query that is ran that
appends the
> records in the history table to another table, I have it this way to
keep the
> users from being able to change the records in the table
>
> Here's the problem - My thought was that the auto numbers did not
duplicate
> themselves - Well on my table they duplicate themselves - One day
you may
> have autonumbers from 1-10 and the next day it starts you on 1
again - What
> is happening because of this is that when the reps are putting in
the
> information and the ID number has duplicated itself the information
is then
> not stored in the table and no error message populates to let them
know this.
>
> Can someone please help me get this straightened out
|
