VB 6 slow on XP?

[DonRI]

I have a VB 6 (SP 6) aplication that runs on Dell machines running Windows 2000 with a 1.70 GHz processor and 1 GB RAM. The application connects to an Access 2000 database on the same machine.

One screen edits about 65 database fields. That screen takes about 2.5 seconds to load.

Recently, I put the application on a few XP machines with a 3.0 GHz processor and 1 GB RAM. With a faster processor I would expect the screen to load faster. Instead, the screen takes 4.5 to 5 seconds to load.

This difference is consistent on all the 2000 and XP machines on which the application is loaded.

Is there something on XP machines that makes VB6/Access 2000 applications run obviously slower? If so, is a fix to the problem available? Thanks.

 

[chiph]

XP is fractionally slower than Win2k, running on identical hardware.

This is not the problem in your case, as the hardware is much more powerful, and the times you're seeing are double what they were. I wouldn't think your problem is with the OS. I would look at stuff like anti-virus, network DNS look-ups, etc.

Chip H.


____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first

 

[PCLewis]

So the application GUI and Access 2000 database are both on the same XP machine?

What database connectivity mechanism ar eyou using in your code? ADODB vi Microsoft's ODBC driver for MDB?

If you had a problem with speed across a network link then I would offer

http://support.microsoft.com/kb/328890/

as worthy of mention. There are no doubt other registry settings that have changed in XP from their defaults in 2000. I would bet that you will have to seek out such a default setting.


I would do the following tests:
1) Unbind your controls from the data source and time how long it takes to load the screen. This test checks(confirms) that it is the data loading taking the extra time.

2) Bind your controls to the data again, but make all of the controls Not Visible. This is testing if the time is in the drawing of the controls. If it is, try again with the win2k gui instead of the default winXP one.

3) If possible, create the same form in Access 2000 and test the load time. This bypasses ODBC and I suspect the load time will be super fast here but it pays to check.

I am sure that those tests will help zero in on the exact nature of the slowdown...

Incidentally, do you have any fileds of 'Memo' or 'Ole Object' type in Access?

 

[DonRI]

I found a similar question about XP speed on another website. In that one, the author says that the VB6 app runs fine on Win 2000 and XP pre-SP2. The author's problem happened when the app was installed on XP SP2 machines and loaded screens that tried to access a database.

I checked the XP machines on which I installed the app and they are both XP SP2 machines. It seems to be the same problem and the culprit may be something in SP2. I am trying to find a non-SP2 machine that I can use to test this possibility.

The better things get, the worse things get.