2010 slower than 2003

[billmeye]

I have noticed a significant slowdown with 2010 compared with 2003. With a simple loop to change control properties in a form with 2010 takes about 4 times longer to complete than 2003 using the same computer. This is an example:

For y = 0 To 639 Step myNumColumns
For x = y To (y + myNumColumns - 1)
Me("Label" & x).Caption = Me("Label" & x).Name & "BILL"
Me("Label" & x).Left = ((x - y) * MyColumnWidth) + MyTimeColumnWidth
Me("Label" & x).Width = MyColumnWidth
Me("Label" & x).Height = MyRowHeight
Me("Label" & x).Top = r * MyRowHeight
Me("Label" & x).Visible = True
Me("Label" & x).BorderColor = MyColorGrid
Next
r = r + 1
Next y


I have tried turning echo off before running the loop and back on after but it did not help. I tried using a construct and that helped some, but not much. I even tried running it on a new Windows 7 DuoCore system but 2010 ran much slower than 2003. It seems that 2007 is 2x slower than 2003 and 2010 is 2x slower than 2007. I was wondering if anyone had any insight into what is going on or any suggestion on how to speed things up using better code.

I've included a sample for evaluation.

Thanks.

 

[gemma-the-husky]

a) its called bloatware - thats why they increasingly demand more and more memory

I am convinced A97 was quicker than A2003

b) but was that a test. or a specific requirement. How do you get/need 640 data elements on a form?

 

[billmeye]

It's a form that ultimately shows an appointment schedule. Depending on the users choices it could show as many as 224 cells. In 2003 it didn't matter since it happened relatively quickly but in 2010 it's annoying the users. My actual code pulls info from various tables to populate the cells such as patient name, phone number, balance due, special instructions, etc. This demo was just that, for demonstrating how painfully slow 2010 has become. It's odd because if you only want to draw the grid of cells without making any changes to the control properties it happens instantly. It's only slow when you are making on the fly changes to the control properties. 2010 seems sloppy in many ways. It flickers more than 2003 between refreshes or requeries and code that seemed to always run perfectly in 2003 sometimes errors for no apparent reason. I'm hopeful of some great fixes in the first service pack release.

 

[boblarson]

See if opening a table (hidden) when you open the database helps.

 

[gemma-the-husky]

rather than thinking of needing to show every cell - you ought to be thinking of extracting a query which just includes the rows in which you are interested

then access can easily construct a datasheet , or continuous form view - and you only have to design the columns in which you are interested. say 7 or 8, instead of 224 - or any other number.

 

[billmeye]

Bob, there are no tables involved in my example. I'm in agreement with Gemma, Microsoft has just carelessly bloated each successive version of the program almost forcing users to upgrade there hardware if they want to stay current. When I run my test code on a newer computer running Windows 7 on a DuoCore it does run much faster, but still only about half as fast as 2003 ran on Windows XP on a simple Pentium 4. I'm disappointed with myself for incorporating features only found in 2010 in my program because I would have been better off staying with 2003. I'm still hoping the successive service packs may help. Thanks for the reply's.