Can a DB be partially corrupt?

[Guest]

I've been working on my AC97 DB for about 9 years and am getting the feeling
its turning into a monster. I have been to this site many times using much of
the advice. Thank you all! Here is what I have done since my visits here.

I have split into FE / BE. All relationships are on the BE.
I run MDE front ends for all users.
Compact BE once a week or more often (there is no auto compact so its a
manual thing). All workstations 'and hubs' are on UPS backups.

But for some reason, I still run into issues that make me wonder if there is
corruption. One main issue is when a typical operation (part number lookup
using combo box) is performed and the DB closes with no warning. Just an
error box stating an error log was created.
I open it again and it continues working fine.
My concern is if my 5 users do the same as above (unknown to me), will this
cause corruption and how do I know?
I just recently imported my BE into a new DB without relationships and
created all new ones. I also imported my FE into a new DB about a month ago.
Still having same issues.
Here are my quesitons.
1) Can a DB be corrupt or partially corrupt without knowing it?
2) Can you identify what is corrupt?
3) Can you tell the difference between it being corrupt or just poor code?
As mentioned above, this DB has grown over the past 9 years. I have
certainly learned a few things about DBs, but am no expert. I worry that
some of the issues I am encountering are my own doing from poor code without
knowing it.
4) I would almost need someone who knows what they are doing to look at my
DB and let me know if they see any major issues. Is this possible?
5) One thing I learned much after the fact was using names (tables, forms,
etc) without spaces in them. Unfortunately, much of my DB has names with
spaces. Will this cause corruption?

Any help and direction would be appreciated.

 

[Len Robichaud]

I have experienced corruption at the record level in a table where
everything works fine until someone tries to edit that particular record
which triggers the problem. The corruption (in my case) was always in a
memo field. I had to scan the table manually, in table view, looking for
"hash" in the field. Sometimes I could delete the corrupt record but more
often even trying to delete the corrupt record triggered the problem as
well. In the end I copied all of the good records into a new table and then
deleted the old table.
Hope this helps.

Len
I've been working on my AC97 DB for about 9 years and am getting the feeling
its turning into a monster. I have been to this site many times using much
of
the advice. Thank you all! Here is what I have done since my visits here.

I have split into FE / BE. All relationships are on the BE.
I run MDE front ends for all users.
Compact BE once a week or more often (there is no auto compact so its a
manual thing). All workstations 'and hubs' are on UPS backups.

But for some reason, I still run into issues that make me wonder if there is
corruption. One main issue is when a typical operation (part number lookup
using combo box) is performed and the DB closes with no warning. Just an
error box stating an error log was created.
I open it again and it continues working fine.
My concern is if my 5 users do the same as above (unknown to me), will this
cause corruption and how do I know?
I just recently imported my BE into a new DB without relationships and
created all new ones. I also imported my FE into a new DB about a month
ago.
Still having same issues.
Here are my quesitons.
1) Can a DB be corrupt or partially corrupt without knowing it?
2) Can you identify what is corrupt?
3) Can you tell the difference between it being corrupt or just poor code?
As mentioned above, this DB has grown over the past 9 years. I have
certainly learned a few things about DBs, but am no expert. I worry that
some of the issues I am encountering are my own doing from poor code without
knowing it.
4) I would almost need someone who knows what they are doing to look at my
DB and let me know if they see any major issues. Is this possible?
5) One thing I learned much after the fact was using names (tables, forms,
etc) without spaces in them. Unfortunately, much of my DB has names with
spaces. Will this cause corruption?

Any help and direction would be appreciated.

 

[(PeteCresswell)]

Per good12find:

1) Can a DB be corrupt or partially corrupt without knowing it?

Yes.

 

[Tony Toews [MVP]]

But for some reason, I still run into issues that make me wonder if there is
corruption. One main issue is when a typical operation (part number lookup
using combo box) is performed and the DB closes with no warning.

One possible answer is that there the number of columns as specified
in the combo box properties is different than the number of columns in
the query.

3) Can you tell the difference between it being corrupt or just poor code?

In this situation it sure doesn't look like a poor code problem.

4) I would almost need someone who knows what they are doing to look at my
DB and let me know if they see any major issues. Is this possible?

Sure. I'd be willing to spend a few minutes reviewing things.

5) One thing I learned much after the fact was using names (tables, forms,
etc) without spaces in them. Unfortunately, much of my DB has names with
spaces. Will this cause corruption?

No. While I use tables and fields without spaces in them I do use
spaces in queries, forms and reports without any problems.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Guest]

Thanks to all.
After doing some digging, I realized there is a SP2b service pack available.
I have been using SP2A. I dont know the difference between the 'a' and 'b'
packs, but I hope this might solve some of my issues.

Tony, if the above doesnt work, I might take you up on reivewing the db.

Thanks!

 

[Tony Toews [MVP]]

After doing some digging, I realized there is a SP2b service pack available.
I have been using SP2A. I dont know the difference between the 'a' and 'b'
packs, but I hope this might solve some of my issues.

Doubtful. It's been my experience that SP a vs b just fixed some bugs
with installed patches.

Tony, if the above doesnt work, I might take you up on reivewing the db.

Email me at tony at granite dot ab dot ca.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/