Database moving records around

[cgilmour2]

Need some help, please. I built a database for work, it currently holds
nearly 50,000 records. Recently, it has started moving and manipulating
records, e.g. today I discovered that record #2 has been completely deleted,
and one of the most recent records has been dropped in near the start - so
that it runs, 1, #deleted#, 3, 4, 5, 6, 7, 8, 46419, then continues 10, 11,
etc. I have no idea where #9 went! The rest of the recently entered ones
are where they should be.

The computer I am using is possibly starting to wear out, and I have heard
that files can be corrupted due to hardware malfunction - is this true, and a
possibility in this case?

Any ideas would be gratefully received. Thank you!

 

[Gina Whipp]

cgilmour2,

Is that an AutoNumber field? Please try sorting the table by that field and
see if they are still *missing*. Now, if you care about sequential
numbering AutoNumber would NOT be the field to use as it only guarantees
uniqueness. ALso if you need them to maintain some kind of ordering, use a
query, it will maintain the OrderBy you set.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[S.Clark]

A table can be sorted by any field, which could cause the ordering of the ID
to be different. Sort the ID column to return it to sequential.

I've never heard of a hardware problem deleting a record, but anything is
possible I suppose.

The #Deleted is interesting too. What are you doing that causes that to
display?

 

[Daniel Pineault]

Corruption can come from numerous sources, amongst others, hadware, network,
the database itself, users, and the list goes on. It can be extremely
difficult to identify. If you truly believe you pc to be the problem switch
pcs for a couple of days to see.

A number of questions come to mind:

- Is your db on a Network or a Local PC?
- Is your db used by multiple people?
- Is your db split?
- Do you have any backups?
- When was the last time you performed a compact and repair on the db?

If your db is showing signs of corruption take a look at
http://www.granite.ab.ca/access/corruptmdbs.htm
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.

 

[Daniel Pineault]

I forgot the most important thing. Before doing anything further, make a
backup immediately!!!
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.

 

[KARL DEWEY]

Recently, it has started moving and manipulating records
How are you viewing the records? if you are looking directly at the table
contents that is the wrong way to view. Use a form fed by a query that is
sorted.

 

[John W. Vinson]

Need some help, please. I built a database for work, it currently holds
nearly 50,000 records. Recently, it has started moving and manipulating
records, e.g. today I discovered that record #2 has been completely deleted,
and one of the most recent records has been dropped in near the start - so
that it runs, 1, #deleted#, 3, 4, 5, 6, 7, 8, 46419, then continues 10, 11,
etc. I have no idea where #9 went! The rest of the recently entered ones
are where they should be.

The computer I am using is possibly starting to wear out, and I have heard
that files can be corrupted due to hardware malfunction - is this true, and a
possibility in this case?

Any ideas would be gratefully received. Thank you!

Tables *have no order*.

A table should be viewed as a sackful of data. If you want to see the records
in a particular order you must create a Query sorting the records in that
order, or use a Report with its Sorting and Grouping property defining that
order. An Autonumber value *is not a Record Number* - it's a meaningless
unique identifier, NOT guaranteed to be gapless or sequential.

It's almost certainly not a hardware problem though there might be some
database corruption. See http://www.granite.ab.ca/access/corruptmdbs.htm for a
thorough discussion of the symptoms, causes and cures of corruption; but I'm
guessing that your data is fine, and you're just making invalid assumptions
about how to look at it!