Converting Access 2000 to Access 2003

[cooldisk2005]

All,
I am working with a guy who uses Access 2000 on his network and is skeptical about upgrading to Access 2003. I will paste his issues below, but I am wondering if there are solutions for his issues? My colleague and I ran into some major problems when modifying the Access 2000 version, so I am wondering if Access 2003 would solve those issues. Here is his email:

Office 11 (2003) is backwards compatible, which means in a perfect world

everything you have should move forward to Office 2003 and maintain all of

its original functionality and provide you additional functionality. Below

are some things to keep in mind when considering changing versions.



Upgrading to Office 11 means moving from Access 2000 to Access 2003. There

are different types of programming code (DAO and ADO) that Microsoft

supports to varying degrees depending on the Access version. Upgrading to a

new version may cause unexpected results and may require code modification.



Additionally, although there are some things that Microsoft still supports,

they are no longer installed by default for example the DAO 3.6 Library

reference. There are other things that Microsoft doesn't support and

therefore will not work in their current form. A current example of that

which you've already experienced is that between Access 2000 and Access XP

the "Calendar Control" functionality was terminated. You used to have the

ability to click on a field in a form and have the Calendar pop up so you

could select a date. But because it's no longer supported, you won't find

it in the database any longer.



Also, since I don't have 2003, until development is complete, we may run

into some of the same issues where you receive an error and I don't or visa

versa, making trouble shooting a bit of a challenge.



One option you will have is how you open the database. Even if you are

working in Access 2003, you have the option of opening and operating a

database in Access 2000 or XP format.



Maybe someone can let me know if there are solutions for his concerns above.

Any information would help.

Thanks in advance.

 

[hermanlaksko]

You can run an access2K (front or back-end) on an accessXP,and vice versa, no problem. I do this every day.

One thing that I have noticed is, that the first time I start, the front-end in my case, it takes a little longer to start, and my guess is that its re-compiling in the background.
This happens even if I am only opening a linked table, but other than that, I have had 0 problems.

Once out of apx. 500 times it happend, that the front became currupt and would not start.
I then created a new empty container (mdb) and imported all elements from the corrupted base and I was up and running again i apx. 5 min.
I am not sure what coused this corruption. Going back and forwards btwn 2K and XP or something else.
Hope this gives you some light on you path. ;-)

Herman
Say no to macros

 

[cooldisk2005]

hermanlaksko,
Thanks so much for this response. This will help tremendously to make a decision.

Thanks again!!!

 

[JoeAtWork]

I open and modify Access2000 databases on Access2003 all the time, so far seamlessly. I can't speak to the calendar control problem, since I've never used it

As far as I can tell, there are very few additions in Access2003. By default, Access2003 uses the A2K format for new databases - so far I've never had a reason to override this to use the 2003 format.