upgrade from ACCESS 2000 to 2003

[Hugh Welford]

Hi,
I am having to upgrade a substantial db application from ACCESS 2000 to 2003

Are there any known issues in this exercise which I should know about and
clue up on before starting on it?

Presume re-compilation will be necessary.

Thanks
Hugh

 

[Allen Browne]

Access 2003 can use an A2000 format database directly. There is no need to
convert to the A2002/03 format unless you want to release an MDE.

Strictly, a recompile should not be necessary going that direction, though I
would recommend it if you modify the code in A2003, and then want to run it
in A2000.

If you suddenly find that A2003 is crashing when you load a form that has a
subform that is based on a query, there is a bug relating to the
LinkChildFields referring directly to an AccessField object (i.e. not to a
control in the subform.)

A2003 can reject a reference such as:
Forms!Form1!Sub1!Text0
which is solved if you use the Form property to refer to the form in the
subform control, i.e.:
Forms!Form1!Sub1.Form!Text0

A2003 can have problems with recognising network printers that work fine in
other programs and earlier versions.

The Themed Controls in A2003 can cause problems with transparency on tab
controls, triple-state check boxes that are not visually distinct, and
flickering of labels that are not directly on the form. More info:
http://allenbrowne.com/ser-46.html

You are probably aware of the crazy security warnings that A2003 gives,
advising you not to use your own database, ... up to 3 times, ... every time
you open it. You will want to dump those by setting macro security to low:
Tools | Options | Macro | Security.

Presumably you are also aware or the impact of other references. These will
need adjusting manually if you referenced the calendar control, MS Graph,
other ActiveX controls, or an Office library such as Excel 9.0. You may also
need to disambiguate things like the Recordset object. More info:
http://allenbrowne.com/ser-38.html

 

[hugh welford]

Thanks Allen

Access 2003 can use an A2000 format database directly. There is no need to
convert to the A2002/03 format unless you want to release an MDE.

Strictly, a recompile should not be necessary going that direction, though
I would recommend it if you modify the code in A2003, and then want to run
it in A2000.

If you suddenly find that A2003 is crashing when you load a form that has
a subform that is based on a query, there is a bug relating to the
LinkChildFields referring directly to an AccessField object (i.e. not to a
control in the subform.)

A2003 can reject a reference such as:
Forms!Form1!Sub1!Text0
which is solved if you use the Form property to refer to the form in the
subform control, i.e.:
Forms!Form1!Sub1.Form!Text0

A2003 can have problems with recognising network printers that work fine
in other programs and earlier versions.

The Themed Controls in A2003 can cause problems with transparency on tab
controls, triple-state check boxes that are not visually distinct, and
flickering of labels that are not directly on the form. More info:
http://allenbrowne.com/ser-46.html

You are probably aware of the crazy security warnings that A2003 gives,
advising you not to use your own database, ... up to 3 times, ... every
time you open it. You will want to dump those by setting macro security to
low:
Tools | Options | Macro | Security.

Presumably you are also aware or the impact of other references. These
will need adjusting manually if you referenced the calendar control, MS
Graph, other ActiveX controls, or an Office library such as Excel 9.0. You
may also need to disambiguate things like the Recordset object. More info:
http://allenbrowne.com/ser-38.html