Network problem: Form Linked to Large Table

[Ganymede]

My company's database is basically built on forms linked to large tables. The tables have gotten very big over the years, and this is becoming a problem because our database is saved on the network. So it takes a while to open the forms. I've taken some steps to simplifying the forms (taking out combo boxes with long queries, etc.), but the problem persists. Is there anything I can do short of splitting the database?

[orange]

Is this a multiuser database?

Why do you fear splitting?

Is there anything I can do short of splitting the database?

Tell us more about the database and the "large tables".
How do the tables get populated?

[Missinglinq]

Having multiple users sharing a single, non-split database, sitting on a network drive, is the sure way to repeated episodes of corruption, as well as speed and timing problems! Multiple users simply have to work off of a split database, with each user having their own copy of the Front End, which contains everything except the data/tables, on their respective hard drives, and a Back End with only the Tables on a shared drive.

Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past ten years have seen literally hundreds of reports of non-split apps causing all kinds of problems! The really insidious thing is that a non-split app can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!

Here are two tutorials on Splitting a Database:

https://www.fmsinc.com/microsoftacce...abaseSplitter/

http://www.hitechcoach.com/index.php...atid=24:design

Linq ;0)>

[Ganymede]

Thank you both for responding. I forgot to mention one key detail in my original post--our database is stored on a server located at the company headquarters. We're based in DC. Headquarters are in Atlanta. So I think that's a big part of the problem.

Is this a multiuser database?

Why do you fear splitting?


Tell us more about the database and the "large tables".
How do the tables get populated?

It is a multiuser database. The large table I speak of has about 25k records. The main input form, which is bound to the large table, contains a subform that logs all of the changes we make to each record on the main form. So the table for the subform is even bigger.

I suppose I fear splitting because I just don't know enough about it. Would I still able to navigate records on a front end database? Most of our database input is for existing records. We rarely create new ones. This problem may be compounded by the fact that we use a lot of subforms. But the data for these subforms will not load on a front-end database, right? So I'm not sure splitting is the answer for us.

Having multiple users sharing a single, non-split database, sitting on a network drive, is the sure way to repeated episodes of corruption, as well as speed and timing problems! Multiple users simply have to work off of a split database, with each user having their own copy of the Front End, which contains everything except the data/tables, on their respective hard drives, and a Back End with only the Tables on a shared drive.

Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past ten years have seen literally hundreds of reports of non-split apps causing all kinds of problems! The really insidious thing is that a non-split app can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!

Here are two tutorials on Splitting a Database:

https://www.fmsinc.com/microsoftacce...abaseSplitter/

http://www.hitechcoach.com/index.php...atid=24:design

Linq ;0)>

Thank you. But my concern is navigation. Would I be able to navigate existing records on a front-end database?