Developing Access 2003 application using Access 2007

[dch3]

I have an Access 2003 app that I support using my personal laptop - which
will soon be replaced with Office 2007 ::jumps behind the couch at the the
thought of the ribbon::. Can I expect any issues with opening the app under
A07 and making changes - adding forms, subs, functions, etc? Unfortunately,
the organization for whom the app is for won't be upgrading for a few months.

 

[Jeanette Cunningham]

Hi dch3,
there is some excellent help and advice here
http://allenbrowne.com/Access2007.html#Bugs


There is also some greate code to manage the A2007 interface in this sample
http://allenbrowne.com/ser-53.html


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[Allen Browne]

Keep both versions of Access on your computer.

You can use A2007 to edit and modify an MDB. But before releasing it,
decompile, compact, open with A2003, compact again, compile, and create the
MDE in A2003.

You probably want to use A2003 to handle manage like custom toobar/menus or
security as well. And to test that you have not used any functionality that
doesn't exist in the older version (such as printing to PDF.)

This list might help:
http://allenbrowne.com/Access2007.html

 

[Albert D. Kallal]

I have an Access 2003 app that I support using my personal laptop - which
will soon be replaced with Office 2007 ::jumps behind the couch at the
the
thought of the ribbon::. Can I expect any issues with opening the app
under
A07 and making changes - adding forms, subs, functions, etc?
Unfortunately,
the organization for whom the app is for won't be upgrading for a few
months.

You can, but I would suggest that you run both 03, and 07 on your dev
machine...and thus can use the same version of access to develop.

 

[bcap]

I have an Access 2003 app that I support using my personal laptop - which
will soon be replaced with Office 2007 ::jumps behind the couch at the
the
thought of the ribbon::. Can I expect any issues with opening the app
under
A07 and making changes - adding forms, subs, functions, etc?
Unfortunately,
the organization for whom the app is for won't be upgrading for a few
months.

I agree with the above, keep Access 2003. Be aware, though, that every time
you switch between 2003 and 2007 an annoying installation will run, which is
particularly slow when going from 2003 to 2007. Make sure that Office 2007
SP1 is installed, because then the installation will be merely irritatingly
slow (without SP1, it's coffee break time).

 

[DaveT]

For most of this year, I've been developing 2003 apps under 2007 and
distributing to clients. THe only thing I have to watch out for is form size
on open, expecially dialog. So the last thing I do is run through the app to
see that ll forms are opening with the size I want.

In my case, I had trouble with 2003 and 2007 co-existing. In any event, I do
have confidence that I can develop 2003 apps under 2007 (Vista machine:
Office 2007, no Office 2003 components) and send to clients without problems.

This includes repair/compact of 2003 mdb's using 2007.

WHile I haven't sent out any 2003 MDE files, you should see:

http://support.microsoft.com/kb/926712/en-us

Error message when you use Access 2003 to try to open an .mde file that you
created in Access 2007: "This database is in an unrecognized format"

 

[DaveT]

One additioanl note. In 2007, set Access Options, Current Database, Document
Window Options to Overlapping Windows.