What are the things I need to watch for? I know about linked table
subdata sheet properties and Sandboxing mode and making sure to run Jet
4.0 SP8 for 2003 but what else should I look for?

We're kind of at the end of the road (so it seems) with Access 97. It
does not play well with Windows 7 Professional even in XP Mode, the
application is crashy/unsreponsive at times.

I figure moving up to a more 'modern' version of Access can help
alleviate some of these problems and allow it to run native in Windows 7
rather than through the virtual XP mode.

So I'm all ears for recommendations on migration or ways to get Access
97 to work properly in Win 7.

Thanks a bunch.

Hi Ryan.
I've been using 2002 and all earlier versions as they were released.
But I've resisted moving on from 2002 until recently, and have now
reluctantly made the jump to 2010 having been pushed by one of my clients.
There is some work involved, and there are significant differences which do
require time to learn.
I've been lucky to receive a great deal of help from this ng on things as
basic as how to use the new help system.
If I was only developing for myself and not clients with changing
requirements, I would probably have stayed with 2002.
However, I'm glad I was 'pushed' and am enjoying the new challenges.
Well that's my two bob's worth anyway.

Bob Darlington
Brisbane
"Ryan" <Mindflux98 (AT) gNOSPAMPLEASEmail (DOT) com> wrote

Ryan wrote:

Moving to 2007 or 2010 would involve a big readjustment (for the developer,
not quite so much for the user). You'd get used to 2003 in a few hours.

XP mode is the only way I could see to install Access 97 on Windows 7

If you are going to do the work, why not move all the way to Access 2010? It
will be a little more work, mostly because you will need to lean about
ribbons. (Yes I know you can import and use toolbars, but IMO they look bad
in Access 2010.)

I recently migrated 2 large Access 97 applications to Access 2010. Most of
the work was fixing coding and design issues that needed fixing in Access
97. All my Access 2010 users have the free Runtime version. The BE is Access
97 because some users have the 97 version of the application.

Along with this group I used information from the following MVP.

http://www.accessribbon.de/en/
http://www.granite.ab.ca/accsmstr.htm
http://allenbrowne.com/tips.html
http://www.members.shaw.ca/AlbertKal.../msaccess.html

I tried the 2007 runtime and my app just threw a bunch of errors (which
I seem to remember the A97 runtime doing the same)

When we use the 'full blown' access setup we don't run into those issues.

As far as Access 2010, the reasoning for maybe just moving to 2003 is
because it's a 'step in the right direction' and we have licenses for
2003.. so costs are minimal.

Thanks for the links, I'll read them soon.



paii, ron wrote:

Rick Brandt wrote:
Well I meant strictly from a code migration/snafu standpoint. Like..
"What gotchas are there in migrating that I have to watch for?"

Ryan wrote:

The only thing I can remember is that form bound check-boxes had some bugs
due to different Null handling in 2003 compared to 97.

There really is no "migration". I develop apps that I publish unaltered in
both 97 and newer versions. There is code that will run on newer versions
that won't run in 97, but anything that runs in 97 will run in all newer
versions.

On 12/22/10 12:13 PM, Rick Brandt wrote:
Alright, well that's promising I suppose.

I guess I ought to read up on ribbons in Access 2007/2010 for good
measure. Converting my menubar didn't come out quite right.

Ryan wrote:
Regardless of which version my users have they get the same classic menu-
bar, tool-bars, and shortcut menus as always with no extra effort on my
part. You only need to convert to the ribbon if you want to.

On Wed, 22 Dec 2010 09:23:29 -0600, Ryan
<mindflux98 (AT) gNOSPAMPLEASEmail (DOT) com> wrote:

I would certainly agree with that plan.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/