Record refresh very slow on clients system. 1

[hcts]

Hi,

I have a client that is using our software. They just had their system crash and they replaced it with another workstation. The problem is that this new workstation is going very slow on record refreshes. IE; We have a table frame that shows each open invoice. The invoice table is linked in the data model to a job and vendor table. At the top of the form are two calculated fields that display the vendor name and job description for the highlighted invoice. Fairly simple. Now on this workstation there is a noticable hesitation (maybe half a second) when you scroll down the invoices listed, but then when you get down to an invoice that is not listed it REALLY slows down. It takes about 3-4 seconds to go from record to record. The system configuration is as follows:

AMD Athelon 2.2 Ghz Processor
512 Meg Ram
ATI Graphics card
40 Gig HD (western digital)
XP Home with SP2 installed and registry entries made for Pdox
PDox Runtime 9, SP2
Norton 2005 Antivirus with app directories excluded from scan.
VNC server for remote access
Brother HL 5170 printer
HP 4070 Scanjet

Now we didn't setup this workstation and the first thing I am going to do is copy the data set to our office and try it there is see if there is data corruption. However, they are reporting this behavior accross the board and I don't think that many tables got zapped all at once.

I am also going to see if we have a copy of XP Home and try to duplicate the enviornment. I have certainly seen Pdox act very weird in certain situations and with some software loaded. If anyone has seen this behavior before and has a tip I would appreciate it.

 

[TonyMcGuire]

Are they on a server (meaning files hosted on another system, not necessarily an actual server OS)? What OS, if so?

If on a server, is opLocks disabled on the server? (See

http://www.tonymcguire.com/oplocks-2000.htm

or

http://www.tonymcguire.com/oplocks-nt.htm

for how to disable.)

Do they have any printers installed that don't actually exist?



Tony McGuire

http://www.thedbcommunity.com

"It's not about having enough time. It's about priorities.

 

[hcts]

Tony,

WOW, that was fast! Wish the record refresh was the same. Yes they are on a server, but I already took that out of the equation. Their tech guy put a UNIX server in. I moved the data to the local HD and got the same results there. Have not checked for nonexistent printers yet. Just to be certain, what do you mean by non existant printers? They have two printers on this workstation that are shared, several printers on other workstations that are automatically listed, and two or three PDF Printers. Could the sheer volume of the printer drivers be causing the problem? (of course it could!)

BTW I just went to another workstation and loaded the runtime there and got the same result. I think the next step will be to try it at the office.

James D. Howard

 

[TonyMcGuire]

Next, ensure that ALL machines that have Paradox have

LOCAL SHARE = TRUE

in the bdeAdmin setup.

This is usually seen as a refresh issue, where new records are added but not seen until later by other systems, but it is worth a try.

Other than that, I'm not sure.

Turn off all PowerSave features. Specifically the NIC card (uncheck 'let OS put device to sleep' or somesuch). Again, not usually these symptoms but...


Tony McGuire

http://www.thedbcommunity.com

"It's not about having enough time. It's about priorities.

 

[hcts]

Again, thanks for the reply. Just to bring the status up to date. I had already checked the Local Share was set to True and turned off all the power saving features. They had no effect on the performance. Now I'm back at the office and have loaded their data on a workstation here and it works fine. I think the best way to tackle this is to reload the OS, install the app and then to reload all the other software one at a time to isolate the problem program. I have seen Yahoo toolbar, Norton antivirus, and HP autoupdate cause this effect in Pdox before. Not sure what else might cause it.

Thanks for the help, I'll let you know what I find out.

James D. Howard