Access 2003 to 2007

Should I expect any issues from upgrading Access applications built on
2003?

I've built a few that are deployed into a Citrix environment, but the
company I'm working for are going to force a 2007 rollout within the
next few months; these applications are project critical and I can't
accept any downtime and need to know if there are any major issues in
a straight upgrade of .mdb's?

Thanks in advance

Luke

On Fri, 22 Aug 2008 06:25:17 -0700 (PDT), lukethegooner
wrote:

You don't have to upgrade anything: A2003 MDB's work just fine in
A2007. Then you can upgrade at your leasure, taking enough time for
testing before you roll out. As with any upgrade there may be a few
incompatibilities or better practices you'd want to take advantage of
(e.g. a Ribbon interface).

-Tom.
Microsoft Access MVP




>Should I expect any issues from upgrading Access applications built on
>2003?
>
>I've built a few that are deployed into a Citrix environment, but the
>company I'm working for are going to force a 2007 rollout within the
>next few months; these applications are project critical and I can't
>accept any downtime and need to know if there are any major issues in
>a straight upgrade of .mdb's?
>
>Thanks in advance
>
>Luke

lukethegooner wrote:

> Should I expect any issues from upgrading Access applications built on
> 2003?
>
> I've built a few that are deployed into a Citrix environment, but the
> company I'm working for are going to force a 2007 rollout within the
> next few months; these applications are project critical and I can't
> accept any downtime and need to know if there are any major issues in
> a straight upgrade of .mdb's?
>
> Thanks in advance
>
> Luke

See http://www.allenbrowne.com/tips.html#Upgrade

Over many years my experience has been that each rewrite of an
application is less tolerant of error and inefficiency than the
previous. I would expect a well-designed and carefully coded mdb
created in Access 2003 to run perfectly, or almost so, in Access 2007.
Access 2007 might balk at bad prectices which Access 2003 allows.
Recently a post here identified a situation in which Access 2007 seems
to behave differently than Access 2003, but I think this procedure,
moving throught the records of a continuous form programmatically, is
not commonly used.


On Aug 22, 9:25*am, lukethegooner wrote:
> Should I expect any issues from upgrading Access applications built on
> 2003?
>
> I've built a few that are deployed into a Citrix environment, but the
> company I'm working for are going to force a 2007 rollout within the
> next few months; these applications are project critical and I can't
> accept any downtime and need to know if there are any major issues in
> a straight upgrade of .mdb's?
>
> Thanks in advance
>
> Luke

Also, when going to Allen's page that Salad gave you the link for, be sure to
read the yellow inset box to the right of the page. This small box has the
answer to at least 75% of all 2003-2007 questions I field.

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

Answers/posts based on Access 2000/2003

Message posted via http://www.accessmonster.com

whatever you don't try to run access 2007 and 2003 in a vista
environment!

most things work, but there are more illegal words to be careful of,
so test!

Regards,
Tom Bizannes
Access & Sql development
Sydney, Australia

Does this address the problems you experienced,Tom:
Errors using multiple versions of Access under Vista
at:
http://allenbrowne.com/bug-17.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"SmartbizAustralia" wrote in message
news:6071d161-efb8-4ba2-a5d1-0ea75ebe93d1-at-v26g2000prm.googlegroups.com...
> whatever you don't try to run access 2007 and 2003 in a vista
> environment!
>
> most things work, but there are more illegal words to be careful of,
> so test!
>
> Regards,
> Tom Bizannes
> Access & Sql development
> Sydney, Australia

Thanks for all your replies. Greatly appreciated.

Luke