Just yesterday I converted an Access 97 database to Access 2000. Have a large
problem I need help with. After converting the DB I "split it" in order to
use it as a backend, same way it was in Access97. After converting the
database to Access2k we began to have a problem with Access2k deleting
records. it deleted a total of 4 out of 62 records. the records are not
together ( record #289365 then 289048 then 289128 then 289178 then this
morning 289405) these record are auto-numbered incerement of one. They were
entered by different people so I know its not just an operator problem. Any
Idea as to why this is happening? Any suggestion will be greatly appreciated.
Thanks in advance.

jmillerwv

On Thu, 25 Oct 2007 07:15:00 -0700, jmillerWV
<(E-Mail Removed)> wrote:

>Just yesterday I converted an Access 97 database to Access 2000. Have a large
>problem I need help with. After converting the DB I "split it" in order to
>use it as a backend, same way it was in Access97. After converting the
>database to Access2k we began to have a problem with Access2k deleting
>records. it deleted a total of 4 out of 62 records. the records are not
>together ( record #289365 then 289048 then 289128 then 289178 then this
>morning 289405) these record are auto-numbered incerement of one. They were
>entered by different people so I know its not just an operator problem. Any
>Idea as to why this is happening? Any suggestion will be greatly appreciated.
>Thanks in advance.
>
>jmillerwv

Are you sure that the records were added, and subsequently deleted? You
*CANNOT* go by autonumber gaps; if you type even one keystroke into a new
record and then hit <Esc> to delete that record, an autonumber gets "used up"
and you will have a gap. That's just in the nature of how autonumbers work!

John W. Vinson [MVP]

Thank you for the reply. Yes I am sure they were deleted in place of the
record in each filed is #DELETED also our work sheet which is printed when
the order is finished in the system exist. inorder to get ride of the
"#DELETED" record I have to repiar and compact the Database. Takes a while at
over 1.2GB.

"John W. Vinson" wrote:

> On Thu, 25 Oct 2007 07:15:00 -0700, jmillerWV
> <(E-Mail Removed)> wrote:
>
> >Just yesterday I converted an Access 97 database to Access 2000. Have a large
> >problem I need help with. After converting the DB I "split it" in order to
> >use it as a backend, same way it was in Access97. After converting the
> >database to Access2k we began to have a problem with Access2k deleting
> >records. it deleted a total of 4 out of 62 records. the records are not
> >together ( record #289365 then 289048 then 289128 then 289178 then this
> >morning 289405) these record are auto-numbered incerement of one. They were
> >entered by different people so I know its not just an operator problem. Any
> >Idea as to why this is happening? Any suggestion will be greatly appreciated.
> >Thanks in advance.
> >
> >jmillerwv
>
> Are you sure that the records were added, and subsequently deleted? You
> *CANNOT* go by autonumber gaps; if you type even one keystroke into a new
> record and then hit <Esc> to delete that record, an autonumber gets "used up"
> and you will have a gap. That's just in the nature of how autonumbers work!
>
> John W. Vinson [MVP]
>

On Thu, 25 Oct 2007 11:52:01 -0700, jmillerWV
<(E-Mail Removed)> wrote:

>Thank you for the reply. Yes I am sure they were deleted in place of the
>record in each filed is #DELETED also our work sheet which is printed when
>the order is finished in the system exist. inorder to get ride of the
>"#DELETED" record I have to repiar and compact the Database. Takes a while at
>over 1.2GB.

Is this a linked table? You normally would only get the #DELETED if the
backend is in SQL/Server or some other database, rather than in JET. Could
something else be deleting the record (other than Access)?

John W. Vinson [MVP]

John,
Yes this ia linked backend with 12 to 15 workstations attached. since I
wrote the first post earlier today I have had several more problems with the
database. It wouldn't allow all users in, it claimed it was opened
exclusivly by another person, a couple of users could get inot the database
but couldn't view parts even though they had permission. I have gotten these
fixed and have had no more problems with the "#DEleting" problem, knock on
wood. I basically had to pull the database down and treat it as a complete
new datbase. had to split it a second time , had to run the user secutiry
wizard, and do a couple of repair and compacts on the db and finally got it
working. I do appreciate your assistance on this matter and if it starts
again I will repost. Thanks all.

jmillerwv

"John W. Vinson" wrote:

> On Thu, 25 Oct 2007 11:52:01 -0700, jmillerWV
> <(E-Mail Removed)> wrote:
>
> >Thank you for the reply. Yes I am sure they were deleted in place of the
> >record in each filed is #DELETED also our work sheet which is printed when
> >the order is finished in the system exist. inorder to get ride of the
> >"#DELETED" record I have to repiar and compact the Database. Takes a while at
> >over 1.2GB.
>
> Is this a linked table? You normally would only get the #DELETED if the
> backend is in SQL/Server or some other database, rather than in JET. Could
> something else be deleting the record (other than Access)?
>
> John W. Vinson [MVP]
>