How to identify corruption.

[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.

 

[Guest]

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

1. Yes. That's why you should make frequent backups.

2. Usually Importing into a new database file often fines corrupt objects.
They won't import.

You can find corrupt memo field records by opening up the table; going to
the memo field; holding down the down arrow key until you get to the end OR
Access shuts down or produces an error. If you were keeping an eye on the
record number, you'll be in the ballpark of the corrupt record. Of course
this method is a problem if you have thousands of records.

Running Jetcomp or Compact and Repair may mention that they found corruption
and even had to delete records.

3. For the most part, bad code just does the wrong thing or nothing at all.
Corruption can shut down Access (with or without warnings), return wrong
records, return garbled records, or freeze Access. It's possible that bad
coding would too.

4. It just takes money and time.

5. Probably not. It could cause code and SQL not to run right if you don't
put [] around the names. More troublesome is using reserved words, such as
Date, for a table or field name. Things can get strange, but that's bad
coding and not corruption.

Your issue with the combo box certainly smells of corruption from here.

 

[Guest]

Hi Jerry,
Thank you for the response - have been spending time reviewing all the
resorces.
Quick question on your white paper - section 2.6 - discribes importing into
a new DB.
It mentiones to turn on hidden and system objects. If I turn on the system
objects, I receive a No Read Permissions error when trying to import the
MSys... tables.
Are these supposed to be selected for import?

Also, I receive a No Read Permissions error when I try to open the
MSysModules table to just view it's contents. Is this normal?

Thanks for your help.
Donovan

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

1. Yes. That's why you should make frequent backups.

2. Usually Importing into a new database file often fines corrupt objects.
They won't import.

You can find corrupt memo field records by opening up the table; going to
the memo field; holding down the down arrow key until you get to the end OR
Access shuts down or produces an error. If you were keeping an eye on the
record number, you'll be in the ballpark of the corrupt record. Of course
this method is a problem if you have thousands of records.

Running Jetcomp or Compact and Repair may mention that they found corruption
and even had to delete records.

3. For the most part, bad code just does the wrong thing or nothing at all.
Corruption can shut down Access (with or without warnings), return wrong
records, return garbled records, or freeze Access. It's possible that bad
coding would too.

4. It just takes money and time.

5. Probably not. It could cause code and SQL not to run right if you don't
put [] around the names. More troublesome is using reserved words, such as
Date, for a table or field name. Things can get strange, but that's bad
coding and not corruption.

Your issue with the combo box certainly smells of corruption from here.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

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.

 

[Guest]

Is there user level security enabled in the database? If so that would
explain it. You need to be logged in as an administrator. If no security,
that would further lead me to believe that there is a corruption problem.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

Hi Jerry,
Thank you for the response - have been spending time reviewing all the
resorces.
Quick question on your white paper - section 2.6 - discribes importing into
a new DB.
It mentiones to turn on hidden and system objects. If I turn on the system
objects, I receive a No Read Permissions error when trying to import the
MSys... tables.
Are these supposed to be selected for import?

Also, I receive a No Read Permissions error when I try to open the
MSysModules table to just view it's contents. Is this normal?

Thanks for your help.
Donovan

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

1. Yes. That's why you should make frequent backups.

2. Usually Importing into a new database file often fines corrupt objects.
They won't import.

You can find corrupt memo field records by opening up the table; going to
the memo field; holding down the down arrow key until you get to the end OR
Access shuts down or produces an error. If you were keeping an eye on the
record number, you'll be in the ballpark of the corrupt record. Of course
this method is a problem if you have thousands of records.

Running Jetcomp or Compact and Repair may mention that they found corruption
and even had to delete records.

3. For the most part, bad code just does the wrong thing or nothing at all.
Corruption can shut down Access (with or without warnings), return wrong
records, return garbled records, or freeze Access. It's possible that bad
coding would too.

4. It just takes money and time.

5. Probably not. It could cause code and SQL not to run right if you don't
put [] around the names. More troublesome is using reserved words, such as
Date, for a table or field name. Things can get strange, but that's bad
coding and not corruption.

Your issue with the combo box certainly smells of corruption from here.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

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.

 

[Guest]

Hi Jerry,
No user level security setup.
Should I be able to view the contents all the MSys tables?

I have had a feeling of corruption for some time, but havent been able to
put my finger on what it is or how to eliminate it.
The main issue has been this error (as mentioned) that appears for no reason.
In fact, I just changed all the 'memo' fields back to text because I read
some possible issues with them.
Thanks

Is there user level security enabled in the database? If so that would
explain it. You need to be logged in as an administrator. If no security,
that would further lead me to believe that there is a corruption problem.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

Hi Jerry,
Thank you for the response - have been spending time reviewing all the
resorces.
Quick question on your white paper - section 2.6 - discribes importing into
a new DB.
It mentiones to turn on hidden and system objects. If I turn on the system
objects, I receive a No Read Permissions error when trying to import the
MSys... tables.
Are these supposed to be selected for import?

Also, I receive a No Read Permissions error when I try to open the
MSysModules table to just view it's contents. Is this normal?

Thanks for your help.
Donovan

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

1. Yes. That's why you should make frequent backups.

2. Usually Importing into a new database file often fines corrupt objects.
They won't import.

You can find corrupt memo field records by opening up the table; going to
the memo field; holding down the down arrow key until you get to the end OR
Access shuts down or produces an error. If you were keeping an eye on the
record number, you'll be in the ballpark of the corrupt record. Of course
this method is a problem if you have thousands of records.

Running Jetcomp or Compact and Repair may mention that they found corruption
and even had to delete records.

3. For the most part, bad code just does the wrong thing or nothing at all.
Corruption can shut down Access (with or without warnings), return wrong
records, return garbled records, or freeze Access. It's possible that bad
coding would too.

4. It just takes money and time.

5. Probably not. It could cause code and SQL not to run right if you don't
put [] around the names. More troublesome is using reserved words, such as
Date, for a table or field name. Things can get strange, but that's bad
coding and not corruption.

Your issue with the combo box certainly smells of corruption from here.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


:

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.