Access 2002 - upgrade

[strangeryet]

Hello, I am currently running Access 2002 Developer. A lot of our users have gone to Office 2003; so there are compatibility issue errors that pop up from time to time in my Access applications, (functions not available etc.)
I'm probably due for an Access upgrade. I need a developer addition so that I can continue to package runtime versions with the applications to install on user machines. What developer version would be less painful to upgrade our current 2002 version databases? I see a developer version for 2003 and also 2007. Any recommendations and any thing I need to worry about with older versions of Access? Thanks

 

[missinglinq]

Allen Browne's site probably has the most complete info updating, going all the way from v97 to v2007. v2003 is probably the most stable version since v97. With 2007 the ability to distribute runtime versions is basically free (money-wise, at least) but 2007 is said to come with a huge learning curve. The most telling comment I've seen said that the learning curve for 2007 for an experienced Access developer was about three times as great as it is for a newbie! Simply said, it's just so different from previous versions! It's also still very, very buggy!

I'm confused by one of your statements.

I am currently running Access 2002 Developer. A lot of our users have gone to Office 2003; so there are compatibility issue errors that pop up from time to time in my Access applications, (functions not available etc.)

If you were running 2003 and your users were running 2002, I could see the problem with some functions not being supported in the earlier version, but the opposite, which you state is the case, shouldn't have this problem.

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!

 

[strangeryet]

Thanks for the info. Yeah you would think the fact that they have office 2003 would not be a problem. Yet certain sql statements from queries that run get caught. At times I have to rewrite them to get them to run in 2003. Others are complicated queries that will run in 2002, (and with users that still have an older office product) but not with the users who have office 2003. And on the other hand, some of the functionality of the queries were pretty basic, like using the Mid statement for instance. I can't tell you specifically what I did but, I had a pretty simple sql statement that used a mid and perhaps another function; Worked for years until 2003 came along, now those users have problems. Could also be a lost reference, but i don't want to persue 2002 issues, when they are using 2003.

Thanks again, I'll look into 2003 for now!

 

[Remou]

If the Mid function is not working, it is almost certainly a missing reference. It is probably best to ensure that the code compiles in 2003.

 

[missinglinq]

I agree with Remou, when standard functions like Mid fail, it is almost always a missing reference, and you don't really have a choice except to check the misbehaving v2003 machines and re-installing them. Otherwise you're going to have nothing but problems.

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!

 

[maggieTan]

Just went through a month of work moving our A2002 to A2007. THere were many little problems along the way. Reference issues, some cose issues and installation issues. Finally have the installation working using the 2007 dev. extensions. It was a lot of grunt work. We maintained the backend in .mdb format so current users can still use their data.

A weird little quirk...even if you package an .mde in A2007, the packager will rename the .mde to .accdr. This has no effect on your front end...but you may have some code or Help files to re-write.