At 5:35 PM -0800 11/17/00, Rachel Zamore wrote:
>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?
The script "Open" in the names file is where this action is. Remove
the steps from this script to stop some of the files from opening.
However, note that you are not saving time, but postponing opening
the files to a later time, when they are called. My experience is
that this is more annoying than waiting for them to open at first.
>
>2. Any other suggestions for speeding up the file loading time?
Faster machines and a faster network are the first two that come to mind.
--
Dave Shaw Northwest Classics, Inc
tel: 206-954-7526 fax: 206-625-1338
