A7.0 Losing Data! HELP

K

KDawes

We are currently using an Engineering DB software that uses A7.0. With this
version we are unable to update to the current verion of Access.

Yesterday we had many entries. Today NONE of them are there! Any suggestions
to why this may be happening? We have stopped all entry until we get some
answers. Unfortunately business must go on. We currently have 35,717 records
in the db.

Thanks for any assistance.

Karyn
 
K

KDawes

Max Size? What is the max size?

Actually, I compact every morning. This mornings routine went just fine. No
problems. The only time we repair is when we receive error notices (ie: 3043
or 3343) from the program.

Also, I had IT load last nights back up that the 'system' does. It occured
around 10 pm. All data is there!

The .mdb is currently 18,386 KB and is usually aroud 16+ after I compact it.

Karyn
 
C

Conrad

The max size is 2GB. Is there any chance that with the data you are adding
that it may be going over that limit?
 
K

KDawes

I double checked with our IT department and the answer is no. When they gave
me a copy of last nights back up it was 18,827 KB before I did the
compression.

About the largest file I see before compression is 24,766 KB and that was
about a week ago.

Karyn
 
C

Conrad

I've got nothing. It could be failing at any number of steps. Can we recap
what you are doing step by step?
 
K

KDawes

Sure. Where would you like me to start?

1) Company has a night shift, but the persons using this sytem go home
around 6-6:30 pm.

2) IT does a nightly backup. However there have been days when we come in in
the morning and the back up is still running (12+ hours!). Today was not one
of them.

3) Each morning I compact the db.
a) I open Access 7.
b) I escape out of the screen where it prompts you for 'an existing db'
etc.
c) I go to Tools, Database Utilities, Compact
d) It prompts me for 'database to compact from'
e) I browse for the correct mdb file and select it.
f) I do give it a new name to 'compact to'
g) Once done I rename the old mdb and update the file name of the new mdb.
h) Then I'm done.

If I have problems I repair first and then complete steps c - h.

Anything else?

Thanks for all your doing ~ Karyn
 
C

Conrad

Why are you escaping out of that dialog box (step b)? You can just open the
database you want to compact/repair and do it right from within the database.
The database will seem to close it will compact/repair and then reopen. No
need to rename or browse or anything.

Do you make sure that the data is the same in both databases. Any chance
that it is truncating any of the records when compacting?
 
K

KDawes

Okay ~ here's the lame excuse for (b): I was taught to do it that way about 5
years ago! I just went out and checked, and If you continue to browse and
select the appropriate DB you get the following error " Device I/O", which I
already know isn't good :-( but I'm working with what I have.

2) Do you make sure that the data is the same in both databases: Are you
asking if I check to see that they both have X # of records? No I don't.
Would I open both and compare the total number of records (lines) in both?

3) Any chance that it is truncating any of the records when compacting?: I
guess that item 2 above would help to answer this.

I can check them against one another, not a problem. But, if the record
numbers are the same (say 10 and 10) how would I know if actual field data is
missing? Todays panic was both records and data.

Karyn
 
C

Conrad

I would defiantly compact within the same database unless I couldn't for
programming reasons.

To check the data there is a few ways. The one I would try first is linking
the table to check (for discussion we will call it TableA) from the Old
database into the new compacted database and run an 'unmatched' query on
TableA compared to TableB(the new compacted database table). If you use the
wizard to create the unmatched query you will have to modify it some but it
should be good.

Hand in there Karyn! :)
 
K

KDawes

Thanks Conrad ~

I will check with our in-house guys to see if they can help me with this.
However, I'm a bit concerned.

Because of the Device I/O error I cannot access this db in any way, shape or
form in Access 7. I have double checked and I can't create new queries or
update(save) any of my old ones in 2000 either. I can only modify (not save)
existing queries to get certain information. Something (don't know what)
happened back in Sept. 03 to cause this.

I think I'm stuck stupid! But, thanks for your support :)

Karyn
 
C

Conrad

Just one more thing. You said this is a 97 database? What version of Office
are you using? If Office is any newer than the database version you will
need to upgrade the database. Check with IT BEFORE doing this.
 
K

KDawes

Well I guess that answers that!

I'm running Office 2000. I already know that the version of Kruse Control we
are using cannot be upgraded to Access 2000, it is not compatible. The new
version (4.0) is compatible, but for good reason we chose not to upgrade. Not
to mention we recently found out they're out of business!

Thanks again ~ Karyn
 
¿

¿Õ°×µÄÖ´Öø

KDawes said:
Thanks Conrad ~

I will check with our in-house guys to see if they can help me with this.
However, I'm a bit concerned.

Because of the Device I/O error I cannot access this db in any way, shape or
form in Access 7. I have double checked and I can't create new queries or
update(save) any of my old ones in 2000 either. I can only modify (not save)
existing queries to get certain information. Something (don't know what)
happened back in Sept. 03 to cause this.

I think I'm stuck stupid! But, thanks for your support :)

Karyn
Click to expand...
 
Top