My computer hosts our database, and I've noticed that it takes up to five+
minutes for ebase (and all its related files) to load on the non-host
computers in our peer-to-peer network when ebase is opened. My initial
thought about speeding this up was to remove all but the most essential
files from the opening script, and then let other files get opened as they
are needed (and as prompts appear to indicate that). I figured I could do
that, and then add files back into the opening script if they appear to be
frequently requested. I just know that we don't use all the files on a
daily basis. Two questions:
1. The opening script I need to change is locked in the ebase file. Should
I make a clone of the ebase file that I can manipulate, or is there another
way around this?
2. Any other suggestions for speeding up the file loading time?
Thanks,
Rachel Zamore
Bay Area Transportation & Land Use Coalition