Network speed

[audiopro]

I am accessing an 18Meg Db over a network. Speed is fine on my office machines but client is complaing that it takes 20 seconds to access on his.

Any suggestions why there should be such a difference in performance. Both netwoks are based on the same model of router.

Keith

http://www.studiosoft.co.uk

 

[GriffMG]

I tend to do what you are Keith, except I don't 'go top', I use an ascending index and 'go bottom' instead.

You can hold the info in a separate table if you wish - I think that is the Mike likes to do it.



Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[Nigel Gomm]

Keith,

glad you resolved it.

Not sure if you've looked into it or not but set coverage is great for finding this sort of problem rather than putting wait windows everywhere. Not using the coverage profiler but instead open up the output from set coverage in notepad/wordpad ; it records every vfp instruction executed by your program with the time it took to execute.

If i ever meet the person who created it they are going to get a big wet sloppy kiss from me.

n

 

[audiopro]

Thanks Nigel
This syetem remains live on my client's computer and wait windows (nowait) were easy for my non computer savvy client. He just read out what the little grey boxes said
The one which stayed on for a while was the culprit.

Since making the change, there is still a delay the first time the code is run but after that the calls are instant, I suppose that is some sort of caching coming into play.

These problems are only coming to light as the table gets bigger but it is still only a tiny thing compared to the ones some of you guys have talked about.

Keith

http://www.studiosoft.co.uk

 

[jimoo]

One more silly thing that has pimped me from time to time. Verify the cleint does not have any network mappings that no longer map to a valid server location.



Jim

 

[TamarGranor]

If this is a multi-user system, any approach that looks at the last record to find out what ID to generate runs the risk of occasionally generating a duplicate. (Specifically, that would happen if two people are adding at the same time: person A gets an ID, person B gets the same ID, then person A's record gets saved, then person B's record gets saved.)

It's much better practice to store the next available value and lock that record while you grab it and update it.

Tamar

 

[audiopro]

Good point but not likely due to the way they operate. One machine in the office for general admin work and one machine in the retail area where orders are placed. Orders are never placed in the office.

Keith

http://www.studiosoft.co.uk