problems with upgrading versions

  • Thread starter Thread starter Glen Rubis
  • Start date Start date
G

Glen Rubis

Can there be problems if a database that was developed
with one version of Access (Access 97, for example) is
then used in a newer version of Access (Access 2000, for
example)? I have heard that this can cause problems but
do not know specifically what they may be. I work for a
county government and am overseeing the upgrade of
an "old" database and we are currently using Access 97.
In the near future many will be upgrading their desktop
operating systems to a newer version of Microsoft Office
(probably Office 2000) and I am concerned that the
database will not be reliable. (There may be a mix of
Access 97 and Access 2000 versions using this database.)
Is Access not a good long-term solution for a database?
Thanks for any help you can give.
 
The tables, queries, form, reports, etc. usually upgrade ok. Sometimes there are issues
with code. Going from 97 to a newer version you are likely to run into an issue with ADO
vs. DAO. Access 97 uses DAO by default, 2000 and newer use ADO by default. The references
in the references window are used in the order that the checked items appear in the
window. The fix is fairly simple. You can use the Up/Down arrows to move the items in the
window or, a better method, explicitly define your items as DAO. For example

Change
Dim rs As Recordset
to
Dim rs As DAO.Recordset

This can usually be done with a search and replace (Ctrl+H) in the code window (Item to
find: As Recordset, Replace with: As DAO.Recordset). You would need to do this for all DAO
items (Database, QueryDef, etc). Also, open the Reference window (Tools|Reference) and
check to see if DAO is checked. If it is, the version should be 3.6. If it still shows
v3.51 checked, uncheck it and scroll down the list and check v3.6.

Have all of the patches for your OS and Office installed before you do the conversion.
Jet4SP7 is the current version, Jet4SP8 should be out shortly (probably in conjunction
with the release of Office 2003). The current MDAC version is 2.8.

Make sure everything is working properly before you try the upgrade. Repair then Compact
the database before upgrading. And BEFORE you do ANYTHING make a backup copy, just in
case.

I have converted several databases from 97 to 2000 without any problems except the one
mentioned above. However, there is always room for a problem to appear.
 
Can there be problems if a database that was developed
with one version of Access (Access 97, for example) is
then used in a newer version of Access (Access 2000, for
example)
Click to expand...

See Wayne's post for the issues regarding upgrading; the only thing
I'd add is that once you've accepted Access 2000's (or 2002's, or
2003's - both MUCH better versions than 2000!) offer to convert the
database, it becomes unreadable by Access97. Be sure you have a
backup, and don't accept the upgrade offer if you have users who
continue to need to read the database in A97.
 
There are several issues to bear in mind when running multiple
versions of MS Access:

Check out the FAQs at: http://www.aylott.com.au/accver.htm


Glen Rubis said:
Can there be problems if a database that was developed
with one version of Access (Access 97, for example) is
then used in a newer version of Access (Access 2000, for
example)? I have heard that this can cause problems but
do not know specifically what they may be. I work for a
county government and am overseeing the upgrade of
an "old" database and we are currently using Access 97.
In the near future many will be upgrading their desktop
operating systems to a newer version of Microsoft Office
(probably Office 2000) and I am concerned that the
database will not be reliable. (There may be a mix of
Access 97 and Access 2000 versions using this database.)
Is Access not a good long-term solution for a database?
Thanks for any help you can give.
Click to expand...


,-._|\ David Aylott (Author of Access Version Checking utility)
/ Oz \ (e-mail address removed) (Melbourne, Australia)
\_,--.x/ Shareware, FAQ, hints & tips at:
v http://www.aylott.com.au/
 
Glen Rubis said:
Can there be problems if a database that was developed
with one version of Access (Access 97, for example) is
then used in a newer version of Access (Access 2000, for
example)? I have heard that this can cause problems but
do not know specifically what they may be. I work for a
county government and am overseeing the upgrade of
an "old" database and we are currently using Access 97.
In the near future many will be upgrading their desktop
operating systems to a newer version of Microsoft Office
(probably Office 2000) and I am concerned that the
database will not be reliable. (There may be a mix of
Access 97 and Access 2000 versions using this database.)
Click to expand...

A mix of A97 FEs and A2000 FEs accessing an A97 BE has been working
just fine at a clients for about the past year or so. Do note that
they're running Jet 3.5 SP3 and Jet 4.0 SP 6.

If you haven't already done so you want to split the MDB into a front
end containing the queries, forms, reports, macros and modules with
just the tables and relationships. The FE is copied to each network
users computer. The FE MDB is linked to the tables in the back end
MDB which resides on a server. You make updates to the FE MDB and
distribute them to the users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at my website for more info. See the Auto FE Updater downloads page
at my website to make this relatively painless.. It also supports
Terminal Server/Citrix quite nicely.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Back
Top