Migrating form Access 2002 to Access 2003

[CAM]

Hello,

Can someone tell me if there are any known issues using Access 2003 with
programs developed in Access 2002. I developed several databases for me
users and they had no problems, but a another database developer has all
kinds of issues, for example forms having calculation doesn't seem to work
properly or Access seems to lock up if a table has been append. Both myself
and my co-worker developed database using Access 2002 and then migrated to
Access 2003. All databases have been splitted (front-end, back-end) and
with password security. Only my co-worker is having this issue, but I don't
have this issue. I know this is a broad questions, but if anybody knows a
website to visit regarding issues with Access 2003, please let me know. I
wondering if my co-worker Access 2003 was not properly installed. Now he
wants to go back to Access 2002 I am not sure if this is a good idea.
Thank you in advance.

 

[Albert D. Kallal]

Can someone tell me if there are any known issues using Access 2003 with

programs developed in Access 2002. I developed several databases for me
users and they had no problems, but a another database developer has all
kinds of issues, for example forms having calculation doesn't seem to
work properly or Access seems to lock up if a table has been append.

there is not any particular issue related to the above. Note that 2002 and
2003 share the same format.

(by the way, access 2003 defaults to a2000 format...are you using a2002-2003
format, or are you using the default
a2000 format? - you should have mentioned this issue).

Usually, problems of failure is related to broken references. Another thing
to try/check is doing a de-compile. That OFTEN fixes problems when moving
between different versions. so, try a de-compile.

You can read about de-compile here:

http://www.mvps.org/access/bugs/bugs0008.htm

And, since it is a bit of a hassle to setup shortcut for each database you
want to de-compile, then grab this handy-dandy registry entry here:

http://www.mvps.org/access/modules/mdl0039.htm

The above adds both a compact, and a de-compile to your right click menu in
the windows explore - *highly* recommend for any budding developer.
(remember to hold down the shift key to by-pass any start-up stuff you have
when sung the de-compile option - and I recommend you exit right after you
do this).

- also, make sure you edit the above registry entry to the CORRECT version
of ms-access you are using....

So, when you move an application with code etc, then it is a REALLY good
idea to do a de-compile on the target machine, and then re-compile the code.
I find this much more problematic when moving a 2003 to a2000, but you are
moving the code to a machine with a different binary format/version...so, it
only makes common sense to de-compile.

If the above don't help, then the next thing to check is for broken
references. When you move an appcation to a another machine (even same
version), then the MOST common problem due to things not working is broken
references. (if you have any word, or outlook or whatever code..remove the
references..and use late binding).

To learn about refs here is some useful links

Allen Browne
http://allenbrowne.com/ser-38.html

Doug Steele:
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

Peter Walker:
http://www.papwalker.com/dllhell/index-page2.html


MsKb Articles: 310803, 208218, 209849, 286300

ACC2000: How Access 2000 Resolves Visual Basic for Applications References
http://support.microsoft.com/default.aspx?scid=kb;en-us;248941

ACC2000: How to Resolve Reference Issues in an Access Database
http://support.microsoft.com/default.aspx?scid=kb;en-us;310803