G
good12find
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.
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.