By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,960 Members | 2,246 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,960 IT Pros & Developers. It's quick & easy.

Upgrading to newer version

P: n/a
Hi

I have an old access 97 application which I need to upgrade to one of the
newer versions. Which of the access versions xp or 2003 should I choose?
Which one is more stable?

Thanks

Regards
Nov 13 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
2003 is more stable and trouble-free than 2002 SP3, so use 2003 if:
- you do NOT need to run the app on Win95/98 machines;
- this is just for you, so you can set the macro security nonsense to No.
Most of the A97 stuff works just the same in the later versions, with a few
exceptions and modifications. However, most of the newer stuff is either of
no benefit for data stored in Access tables, or else does not work properly
or is a hindrance to productivity/performance.

Some pointers:
1. Consider keeping your A97 as well as A2000. You can do that with a custom
install of Office 2000. If you have any difficulty getting them to co-exist,
see michka's article at:
http://www.trigeminal.com/usenet/usenet019.asp?1033

2. If a database will not convert, use A97 to decompile it first. While
Access is not running, enter this at the prompt. It's one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

3. If you use ActiveX controls (such as calendar), the version will probably
break when converted. Fix it through References on the Tools menu (from a
code window).

4. By default, A2000 and 2002 do not include a reference the DAO library, so
you need to set up a reference to Microsoft DAO 3.6. More info. on
references:
http://allenbrowne.com/ser-38.html

5. A2000/2002 do include a reference to the ADO library, which duplicates
objects such as Recordset, Field, Property. Either remove the ADO reference,
or explicitly disambiguate everywhere in your application, e.g.:
Dim rs As DAO.Recordset

6. The "Name AutoCorrect" has myriads of bugs and performance problems. Turn
it off immediately you create any A2000 database. More info:
http://allenbrowne.com/bug-03.html

7. There are new properties that give performance problems (such as
SubDataSheetName for tables), and some existing properties have had their
defaults changed in a way that could compromise your validation code (e.g.
AllowZeroLength for code). More info:
http://allenbrowne.com/bug-09.html

8. There are serious problems with some of the new features in JET 4, such
as the Decimal data type. More info:
http://allenbrowne.com/bug-08.html

9. Access 2000/2 is incapable of saving just the object you are changing
like
A97 does. That means concurrency problems (2 people cannot work in different
objects in the same mdb at once), and it takes longer to save if the mdb has
many objects.

10. Instead of the integrated development environment in A97, A2000 and
later have a version of Visual Basic cobbled together with the main Access
window. That's handy if you with with dual monitors, but does cause other
problems from minor annoyances with way the windows behave through to Access
getting completely confused about what goes with what if you have different
versions of Access open at the same time, thereby corrupting the database.

11. It is absolutely essential to have the service packs for A2000/2. The
bugs
are so many and so drastic that simply importing code from A97 and closing
your database is enough to corrupt it if you do not have the service
packs!!! Details:
http://support.microsoft.com/?id=304548

12. Many of the known bugs in A97 have not been fixed. Hundreds more were
introduced in A2000, and many of those remain unfixed in A2003. In our
experience, you can expect to waste time with a couple of new bugs you have
not come across before in every mdb you develop. Some of these are listed
here:
http://members.iinet.net.au/~allenbr...ips.html#flaws
--
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.

"John" <jo**@nospam.infovis.co.uk> wrote in message
news:40**********************@news-text.dial.pipex.com...

I have an old access 97 application which I need to upgrade to one of the
newer versions. Which of the access versions xp or 2003 should I choose?
Which one is more stable?

Nov 13 '05 #2

P: n/a
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in
news:40**********************@per-qv1-newsreader-01.iinet.net.au:
4. By default, A2000 and 2002 do not include a reference the DAO
library, so you need to set up a reference to Microsoft DAO 3.6.
More info. on references:
http://allenbrowne.com/ser-38.html


That's not relevant if you're converting a database that has a DAO
reference already. It's only valid for MDBs created in A2K or A2K2.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #3

P: n/a
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in
news:40**********************@per-qv1-newsreader-01.iinet.net.au:
7. There are new properties that give performance problems (such
as SubDataSheetName for tables), and some existing properties have
had their defaults changed in a way that could compromise your
validation code (e.g. AllowZeroLength for code). More info:
http://allenbrowne.com/bug-09.html


My copy of A2K does *not* have ZLS allowed by default.

A2K2 *does* have ZLS allowed by default.

What a bloody stupid error on the part of Microsoft.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #4

P: n/a
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in
news:40**********************@per-qv1-newsreader-01.iinet.net.au:
12. Many of the known bugs in A97 have not been fixed. Hundreds
more were introduced in A2000, and many of those remain unfixed in
A2003. In our experience, you can expect to waste time with a
couple of new bugs you have not come across before in every mdb
you develop. Some of these are listed here:
http://members.iinet.net.au/~allenbr...ips.html#flaws


Allan, your work writing up these "flaws" is excellent. I had never
seen this collection of your articles before, and read them avidly.
And I learned far more than I expected -- I did not know that the
Bookmark bug still existed.

I was thinking, though, that you might refer to the workaround for
the Bookmark bug, which is requerying after a delete if you're going
to navigate by bookmarks (which is probably more a best practice
than it is a mere workaround).

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #5

P: n/a
Thanks, David.

This question has been asked several times in the last week, so I've spent
several hours in developing the list into a new web article. Available at:
http://allenbrowne.com/ser-48.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.

"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@24.168.1 28.86...
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in
news:40**********************@per-qv1-newsreader-01.iinet.net.au:
12. Many of the known bugs in A97 have not been fixed. Hundreds
more were introduced in A2000, and many of those remain unfixed in
A2003. In our experience, you can expect to waste time with a
couple of new bugs you have not come across before in every mdb
you develop. Some of these are listed here:
http://members.iinet.net.au/~allenbr...ips.html#flaws


Allan, your work writing up these "flaws" is excellent. I had never
seen this collection of your articles before, and read them avidly.
And I learned far more than I expected -- I did not know that the
Bookmark bug still existed.

I was thinking, though, that you might refer to the workaround for
the Bookmark bug, which is requerying after a delete if you're going
to navigate by bookmarks (which is probably more a best practice
than it is a mere workaround).

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

Nov 13 '05 #6

P: n/a
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in
news:40**********************@per-qv1-newsreader-01.iinet.net.au:
This question has been asked several times in the last week, so
I've spent several hours in developing the list into a new web
article. Available at:
http://allenbrowne.com/ser-48.html


Excellent (and my apologies for mis-spelling your name, Allen!).

One suggestions:

In regard to the DAO compatibility library -- maybe you should make
explicit that it's better to remove the dependencies in A97 and get
it all working before the conversion. That's probably obvious to
those of us who are experienced Access programmers, but not so clear
to novices to the conversion process.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #7

P: n/a
Will do. Thanks.

--
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.

"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@24.168.1 28.78...
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in
news:40**********************@per-qv1-newsreader-01.iinet.net.au:
This question has been asked several times in the last week, so
I've spent several hours in developing the list into a new web
article. Available at:
http://allenbrowne.com/ser-48.html


Excellent (and my apologies for mis-spelling your name, Allen!).

One suggestions:

In regard to the DAO compatibility library -- maybe you should make
explicit that it's better to remove the dependencies in A97 and get
it all working before the conversion. That's probably obvious to
those of us who are experienced Access programmers, but not so clear
to novices to the conversion process.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

Nov 13 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.