You can use your favorite social network to register or link an existing account:
Or use your email address to register without a social network:
Sign in with these social networks:
Or enter your username and password
Forgot your password?
Yes, please link my existing account with for quick, secure access.
No, I would like to create a new account with my profile information.
I want to thank everyone who participated in our last thread on backwards compatibility. There is lots of great discussion about how the decisions we make will impact your business. Folks are reading it and digesting the feedback. Again, thanks.
Recently, I came across a great article that compares Windows XP, Vista, and Windows 7 performance by Adrian Kingsley-Hughes on ZDNet. He put the three operating systems through a series of real-world tests to find out which one was fastest. Adrian picked 23 straight-forward tests. The first five tests were:
Adrian gave each operating system a 1, 2, or 3 based on which one was fastest. The Windows 7 Beta placed first in nearly every test--kudos to the Windows 7 team.
How does this relate to Access? Good question…
What scenarios would you pick for a similar test for Access 14 ? Are there scenarios where Access feels slower than you would expect?
Are there areas where Access 2007 is slower than Access 2003? We have fixed a few performance issues in SP1 with more coming in SP2; however, the team still wants to make sure our performance efforts are getting the most bang for the buck. If you have a repro case where 2007 is slower than 2003, send us email. Our performance team would love to take a look.
BTW – I’m pinged daily about Access 14 Beta 1. In December we ran a developer kitchen for 30+ Access pro devs who came to Redmond, used the latest build for 4 days, and gave us feedback. The team is now busy incorporating their feedback and getting ready for Beta 1. The Beta 1 date hasn’t been announced yet so I can’t talk about it. If you are interested in participating in the Beta keep an eye on this blog--more information is coming about how to get involved.
Access 2007 is much slower than other Access versions when starting up after having opened a different Access version. I spend way too much time watching the "preparing to install...", and configuration messages before the application opens. This has improved greatly since the beta version, but it is still an issue.
I was just compacting a large database and was reading blogs in Google Reader and this one come up. So, how about comparing the speed to Open a large database, compress it and close it? Look forward to the beta...
I would welcome an improved performance when MS Access is used from shared folders within a network. I do not have any comparison between different versions of Access in this scenario. But both Access', 2007 as well as 2003, "feel" very slow even when used at fast networks (e.g. 100MBit/s LAN), and little amount of data (Access file size <2MB). I know, this use case should usually be covered by database systems like MS SQL or competitors. But many of my customers are working great with "MS Access over network" (three or four people working at the same database) rather than all working on the same Excel file.
Even Access was allegedly accused of stealing Foxpro technology, it was still left in the DUST compared to VFP as development tool and application on performance issue.
My clients and I have found that start up is significantly slower, and I definitely find that ribbons sometimes dont refresh for a few seconds. Our primary solution is an ADP and I do not find any difference in data processing between 2002\2007, although I haven't done any benchmarking.
There seems to be an issue that there is no Access Design support for queries in an ADP application that has been ported to SQL Server 2008.
Access 2007 is a bit deceptive when loading up for the first few times because it has a “far nicer” startup page. When I first launched 2007 it loaded a good deal slower then previous versions and I was REALLY worried. However, if one clicks on an actual mdb or accDB file, then that pretty startup page is by-passed, and in these cases the startup time is really very much the same as pervious versions. I am hard pressed to see the difference in startup times when not allowing the pretty startup page to launch. Hence, don’t judge the startup time by loading just launching access and THEN opening your application. Try clicking on the application and when doing this, I found application load times are very good (very close to pervious versions). I even been running a2007 on my older 3 year old notebook with a budget single core semprom processor and again load times have been very good for me. The large application I was working on was not running on a network. However, it did have 250+ forms and over 100,000 lines of vba..and it loaded/ran well. I have to save comments on network performance until next month when I convert some of my older applications that are split over a network to a2007. So far however, I quite deep in to using a2007 and it been good in terms of performance and I’ve not really identified a particular performance bottleneck. The only performance issue that bit me was larger SharePoint tables over wireless, but then again that’s a different issue! And not a surprise! Anyway, quite impressive to see the access team asking in public for us users to bring up any performance issues! So, if I do find anything, I be first in line to bring it up with you folks! So far…it been good! Albert D. Kallal (access MVP)
Edmonton, Alberta Canada
A good place to start would be the EULA, where currently your lawyers make it really scary to publish performance reports. I have tried to get other newsgroup regulars interested in this several times, but no takers for that reason.
Well i'm in the middle of upsizing a 97 mdb to a 2007 accdb. The mdb uses linked tables from SQL Server2000. This works like a rocket. When I did the upsize to a Vista client on access 2007 in combination woth SQL2005 Express edition I saw a big performance drop. This really worries my client because he won't migratoe to 2007 if i can't get my finger on this problem. So far all I read on these issues is that the backend might be poorly designed. Agreed, but i'm not allowed to change that and why is is performing so well in access 97. Beats me. To make my point we both started the same app. one in 97-sql2000 and one in 2007-sql2005express. The form in 97 took 1 second to fetch the data where the form in acc2007 on vista to 10 seconds to fetch the data. Unfortunately i'm not allowed to use this for a case for microsoft because it has confidential info in it but it's just to make a point. Installed every possible hotfix there is. Don't get me wron I love Access 2007 but in this particular situation i'm beat by access 97 ;-(