Using Access 2013 to make changes to DB in Access 2003

[lisarmj]

I have a new client who has asked me to assist in making some changes to a database which was developed in Access 2003. The company is still using 2003 with no plans to upgrade.

My computer is running Access 2013. Can anyone provide advice before I start this project?

I'd like to avoid conversion problems, reference errors, and using functions which are not available in 2003. Also, I believe their last developer (who is unfortunately deceased) distributed the Front-Ends as .mdb files. What is the best way to distribute the front-end especially if I am working in a newer version of Access than the client? The front-end will be loaded on all their salespersons laptops as well as several in-house personnel.

Most of the work I do is for single users and any advice would be appreciated.

Thank you!

 

[spikepl]

Test how smart A2013 is . Take a copy of your MDB file, create a split form there (that's an A2007-feature) if it lets you, and see if it lets you save retaining the MDB format.

For distribution - first check what the current procedure is, no need to touch things that people are familiar with, unless some huge gain is apparent.

 

[Galaxiom]

Developing in a later version is a potential nightmare even if you try to avoid the later version features. You can still work with an mdb file but that mdb can still take on 2007+ features which will fail in A2003.

Applications are best distributed compiled. No matter what features you avoid, an mde compiled by A2007+ will only run in the Runtime for the version it was compiled in or later.

Support for Office 2003 has ended. If they won't upgrade they should abandon their ability to develop and start using the runtime of a later version.

 

[Mike375]

My experience is that it is a hit or miss deal.

The 2003.mdb will run without changes in. At least that has been my experience on a couple of versions of very complex 2003 mdbs. Among other things these mdbs have a lot of instances where they open Word and fill bookmarks or open Excel and fill cells and also on close macros in Word and Excel sending data back to Access text boxes.

This running them as Access 2000 File Format

HOWEVER. if these 2003 mdbs are simply run in 2013 there are problems if they are put back on a computer with 2003 and for both Vista and Windows 7.

Some smaller less complex 2003 mdbs have been OK after both running in 2003 as well as making some changes, not big changes, mainly to form design and then run them back on a 2003 computer and they have been fine.

The first thing I would try if I was you is have copy of the 2003 mdbs in question run on your 2013 and then see how they go when run again on a computer with 2003. If there are problems you can forget making changes.

Having said that I have tried with a couple of 2003 mdbs that would no longer run properly after being in 2013 environment, to make a blank data base in 2003 and then import everything.

If you put a 2003 in 2013 you will see that even though it is left as a 2003 in design view tables and also macros will look as if they were 2013.

Your clients (and your) best interest is go to 2013. In Australia it is $12AUS per month and that allows it to be on 5 computers. If you get MS Office professional on disk it is about $600 and only useable on one computer.

Edit: The above is based on 2013 being on Toshiba computers with Windows 8.1 64 bit

 

[CJ_London]

since they are insisting on using technology that is no longer supported, suggest you ask them if they have a spare laptop with access 2003 you can borrow to make the changes - you can still backup to your machine.

 

[Frothingslosh]

In addition to everything said above, one thing to keep in mind is that opening an Access 2003 database in Access 2013 WILL result in broken references for Access 2003 users, even if there are no problems with A2013.

We have both here at work, and I get to fix this problem at least once a week. The main things are that you will need to uncheck any missing references, check the reference for Microsoft DAO 3.6 Object Library, and check the references for any MS Office references that show MISSING, as A2003 won't select, say, the Microsoft Excel 11.0 Object Library if the reference for the Microsoft Excel 15.0 Object Library was checked. Also, one of the missing references will be the Microsoft Office 15.0 Access database engine Object Library - you can ignore that one as long as you've enabled the DAO library, as it has no direct match in A2003.

 

[anujkmehrotra]

I recently upgraded my 10 years old project [mdb] into new [accdb] few days back and found no problem with that. But update A2k3 32bit to A2013 32bit. A few little changes in references and settings only.

Hope for the best.