Split DB with Compact and Repair

[Dugantrain]

Hi, after several crashes making my db virtually unuseable in a multi-user environment, I have decided to bite the bullet and go ahead and try to split this thing up (previous attempts to split the db made it extremely slow, but I guess a slow db is better than an unuseable one). I'd like to know the best format for Compact and Repair; should I have the back-end as well as all local front-ends automatically C & R on close? Or is there a better format? Also, any advice on hurrying the db up would be appreciated. What would you think about partitioning the shared drive so that the back-end is on its own drive and shared with no other files? I'm not a network guy, so I really don't know.

 

[Autoeng]

Setting Compact On Close should be ok becase it won't fire until the last persons exits the db. You shouldn't notice any problem with doing everytime. That way you don't have to remember when the last time you compacted was.

Autoeng

 

[Dugantrain]

Well, that definitely answers the first part of my question. I hate to reopen a topic that has been explored to no end in these forums, but is there any definitive answer that anyone has found to speeding up calls to the back-end? I've retested the split db and the sad fact of the matter is that we cannot go forward in this state (users must call 20-30 different reports/queries/forms a day, each one taking 1-3 minutes to load).

 

[llkhoutx]

Have you tried keeping all required forms & reports open, but hidden except when actually being used. Without knowing more about your program, the "load" time you're experiencing may be a result of the combined "load, open & compile time" required on opening a specific form and/or report. This technique does require more than minimal RAM when other programs are also used.

 

[Dugantrain]

Hmmm...So you're suggesting to have all objects that make calls to the back-end load when the db opens, have all of their Visible Properties set to False, and then set each object's property set to True when it is clicked on the Switchboard? How much worse would the initial load time be, as I have a dozen or so objects that would need to be loaded? Also, is it possible to Hide/Show a query? For the record, all objects that do not call the Back End load quickly, so I don't think it's a code/compilation issue.