Constant repair issues

[Agism]

Somebody please help me. I am getting errors when opening my database that says it is not a database format and needs to be repaired. I seem to be gettting it more frequently lately as well. Here is my situation:

I have 3 databases. One backend with all the data that is 25.7MB. One frontend 'A' that only 2 people use and are in all day that is 14.5MB. And a second frontend 'B' that up to 7 people are in at any time of the day that is 7.31MB. I just recently split the original database into these three when the 7 people began using it. I was hoping to avoid the repair problems.

Twice now, the 7 person front end has needed repairs. Just now, the backend needed repairs. One person was listed as a suspect and was listed 3 times. He was currently in 'A' and had entered 'B' twice. With one form open, he closed the entire database 'B'. When he went to re-enter a few minutes later, the database needed repairs.

Is there a problem when both front ends are opened on the same computer?

Is there a "right way" and a "wrong way" to exit a database. (Should all forms be closed?)

Any ideas would be helpful. I feel like I am a little over my head with this issue. Argh!

 

[Shep]

Hardware problems can cause sudden loss of network connectivity; this may be what's happening on the suspect logins.

Not that it's the source of your corruption, but it IS a very good idea to build an .mde from your frontends, and distribute a copy to each user. They really shouldn't all be logging into the same frontend.

Opening both frontends on one machine is likely not the source of your problem.

I'd start with replacing patch cables for all 9 workstations and go on from there.

You may also consider disabling opportunistic locking on the server, depending on what O/S it's running and on some other factors.

Also check Knowledgbase article Q303519 (Access 97) and/or Q300216 (Access 2000).

Using reserved words and characters can also cause corruption, as can using the word "Application" as a field name.

Under some conditions, not compacting can also cause corruption.

Not expecting corruption can cause corruption.

Shep

 

[Agism]

Thanks

Thanks Shep! The knowledge base article has given me a lot to think about.

Right now, distributing the front end isn't an option. Most of the people working in the database are part-timers and I never know which computer they are going to be working on.

I backup the backend every morning and compact it as well. And I don't believe I am using any reserved words.

But now I have a few other things to check.

By the way, where in Houston are you? I moved from there a year ago. Sometimes I miss it. I certainly don't miss the traffic!

 

[Shep]

So put a copy on all workstations, problem solved. heh heh

I work in Clear Lake/NASA area, but have bought a home in Katy. Yeah, the traffic wears on the old brain, 55 miles drive to the office, takes about 1.5 hrs.

 

[Agism]

Katy! Good grief.

How funny, I grew up in Seabrook. El Lago to be exact. What a small world.

I stay to chat, but this database is acting up again. This time it corrupted as someone was editing a record. Now that record doesn't exist. No worries since I have a back up from last night that I can get the information from. But I can't believe it is having so many problems. There has to be a better way.

 

[Shep]

If the user in question did not also experience a loss of network connectivity, I would be surprised.

If not, then you really have your work cut out for you.

 

[ilir_]

Maybe you should consider upgrading you database in SQL (MSDE) and convert the .mdb to .adp

 

[Agism]

ilir_ - I don't have access to SQL. Thanks for the suggestion though.