slow FP on windows

[Bill Vermillion]

On Thu, Feb 03 10:27 , Richard D. Williams, showing utter disregard for 
spell-checkers gave us this: 

> I have only one client still using FP for dos/windows. They
> have a win 2000 server. I don't do a lot of work for this
> client, but I have noticed extremely slow performance when
> posting to any file.

Slow compared to what?  I suspect it's always this slow.

> PFDSK is set to the shared drive of F:.  Filepro resided in F:\fp and 
> filepro files in F:\filepro.

> Is there some other environment variable I should set. This
> thing takes 5 mins. to post 379 records. The processing table
> is only opening one file and creating a new record for each
> source record. I did not write the code, but I can see no
> reason this should take so long. In SCO or RH, it would be a 30
> sec - 1 min. process.

> Any suggestions?

When I migrated an office running on a 16Mhz Xenix machine to
the 200MHz Pentiums on a Novel network a print job that took
15 minutes to spool and 3 hours to print [slow HP2] took
8 hours.  Everyone blames filePro and I had to figure out a way.

For posting this won't help but it certainly will for large print
jobs.  For print jobs direct the output to a file on the local
printer.  In this case that took about 30 minutes - instead of the
origal 15.   Then when the job is done direct that back to the
print servers.   That way the loca PC was out of use for under and
hour - though the print job across the network still took about 8
hours instead of about 4 when locally connected on Xenix.

Any thing you can do to keep things from being bi-directional
and split it to do everything to and on the local PC and then send
it back to the server will help.

If you can build a file on the local machine, move it to the
server, and post from the server it may help.  However with
just a few hundred records it may not be worth it.


-- 
Bill Vermillion - bv @ wjv . com