Question New employers - new version of Access

[ed1967]

[FONT=&quot]Hi all

I've just moved from one employer to another. My former employer was still using Access 97 when I left - about six weeks ago - my new company uses Access 2010. Although I've used Excel 2010, Word 2010, etc, I've had no experience of Access 2010 til now.

I'm aware of all the changes, but are there any particular pitfalls or issues that anyone would recommend that I should look out for in this new environment? What specific unexpected problems has anyone come across when upgrading direct from 97 to 2010 (without any of the interim releases)? (All the databases at my new employer have already been migrated, so I don't have a problem there - just need to know what changes I need to make to my way of working).

Cheers

Ed

(Apologies if this is in the wrong forum)
[/FONT]

 

[CJ_London]

My personal opinion.

It is all pretty much the same - obviously the gui is different and there are new features in 2010 which are not in 97 - seems primarly to try and encourage Excel users and generally I would avoid.

One major change is moving from DAO to ADO and of course there is now the existence of 64 bit which has an impact primarily on API calls if you have a mixture of 32 and 64bit machines

Once you get used to the new GUI you shouldn't have a problem

 

[boblarson]

ADO is being deprecated so stick with DAO.

Pat:

Just curious where you heard that one. This is the first I've heard about it. Is it new since the MVP Summit in Feb 2012? I, of course, wasn't at the 2013 one so don't know what may have been covered there.

 

[CJ_London]

Pat - a good reason fur using late binding!

 

[CJ_London]

Pat- Re 32/64 bit machines

Sorry, I should have been clearer, I meant 32/64 bit Office, not windows