Re: indexes and relationships blown away sometimes

Tech-Archive recommends: Fix windows errors by optimizing your registry

Nobody touches it. They have no idea how and they don't have time. The
changes are too random as well.


"Jerry Whittle" <JerryWhittle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B1E4E679-E857-42ED-9CCA-97D7FDB6101F@xxxxxxxxxxxxxxxx
Is the app locked down and only a few people can get to the table design?
I've seen users mess with things like primary keys when they became "too
much
trouble".
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"Keith G Hicks" wrote:

Access 2000 w/ jet backend.

This client of mine runs the app in a pretty harsh environment. Long
cables
(and poor quality ones at that), no boosters, very hot temperatures (the
air, not the employees, LOL) and impatient operators. Some time ago I
noticed that some of the relationships were blown away and primary key
fields were no longer primary keys. Once in a while I'd have to recreate
a
few of them as needed. After a few years of littel contact with them I've
found that the problem has gotten worse and the current data file is full
of
corruption. Of all my Access clients, this is the only one I've ever seen
with this level of corruption.

Allen Browne's site has this section:
http://allenbrowne.com/ser-47.html#LostKeyRelation

But he doesn't say why indexing rules could be violoated. I'm wondering
how
much the hardware has to do with this. I'm also wondering how Access is
letting duplicate PK's into tables so that the compact & repair ends up
deleting indexes and FK's. I'm hoping that if they upgrade some network
gear
that the problem will be reduced significantly. I'm also wondering how
much
help it would be for me to convert this thing to MS SQL on the backend. I
did that for another client and corruption was reduced but they didn't
have
any where near the problems that this client has.

Thanks for any input,

Keith





.

Quantcast