upgrading from Access 97 to 2003

[Will]

I have 18 users using Access 97 application on their local
systems, and using a single database file on the server
that was created in 1997 with over 200,000 records in the
main table. The database file is only 70 MB's in size, and
I know the theorectic limit is 1 GB.

We are starting to have occasional strange errors which I
won't go into detail. I have to do a "Tools, Utilities,
Repair Database" about every two weeks.

My question is, if I purchase Access 2003 and convert the
data, is 2003 much more stable than 97? Or does it even
matter. Is A-2003 just more bells and whistles? Which I
don't need. It would be a costly upgrade.

The answer is probably obvious, but are there serious
arguments to upgrading, regarding stability.

One reason we have never upgraded is because 97 has been
surprisingly stable. Also we use pivot tables quite a bit,
and I saw in Access 2002, that pivot tables are very
different than in 97. Way less user friendly.

Thanks in advance.

 

[Douglas J. Steele]

Did anything change in your network recently? Often what you're experiencing
is symptomatic of a faulty NIC card, since Access is very sensitive to
network issues. Access 97 is one of the most stable versions: I doubt very
much upgrading to Access 2003 would make a difference. (Of course, there are
other reasons to upgrade, such as the fact that Microsoft has dropped
support for Access 97...)

You might take a look at the Corrupt Access MDB FAQ Tony Toews has at
http://www.granite.ab.ca/access/corruptmdbs.htm

 

[Allen Browne]

Like Doug, I do not believe that upgrading will solve the corruption issues
you mention.

To answer your broader question, my experience is that you can configure
A2003 so that it is a more stable *development* environment than A97. There
are several issues though, and we have detailed those in this article:
Converting from Access 97 to 2000, 2002 or 2003
at:
http://allenbrowne.com/ser-48.html

 

[Tony Toews]

I have 18 users using Access 97 application on their local
systems, and using a single database file on the server
that was created in 1997 with over 200,000 records in the
main table. The database file is only 70 MB's in size, and
I know the theorectic limit is 1 GB.

We are starting to have occasional strange errors which I
won't go into detail. I have to do a "Tools, Utilities,
Repair Database" about every two weeks.

Single database?

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 http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm 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

 

[Guest]

I was hoping you were going to say it is more stable.

I am not a developer, just a GUI type of Access creator. There are no network issues. And I have split the FE and BE before, but the queries took far longer to run, along with pivot tables. So I rejoined them. And that doesn't really have anything to do with this issue.

I will just purchase Access 2003 and test the conversion before I go and invest in 25 user licenses.

I appreciate all of your comments.

Will

 

[Rick Brandt]

I was hoping you were going to say it is more stable.

I am not a developer, just a GUI type of Access creator. There are no

network issues. And I have split the FE and BE before, but the queries took
far longer to run, along with pivot tables. So I rejoined them. And that
doesn't really have anything to do with this issue.

I will just purchase Access 2003 and test the conversion before I go and invest in 25 user licenses.

I appreciate all of your comments.

Just so you can hear it again. While I still would not recommend it,
Access 97 is MUCH more tolerant of having multiple users running the same
monolithic application than the newer versions. If you have an occasional
corruption now using A97 it will be a LOT worse after you convert if you
don't also split at the same time.

 

[Tony Toews]

I was hoping you were going to say it is more stable.

I am not a developer, just a GUI type of Access creator. There are no network issues. And I have split the FE and BE before, but the queries took far longer to run, along with pivot tables. So I rejoined them.

The three most common performance problems in Access 2000 or newer
are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

And that doesn't really have anything to do with this issue.

Actually a combined MDB possibly has everything to do with your
strange troubles. And you will run into a lot more problems and
corruptions in A2000 and newer with a combined MDB.

I will just purchase Access 2003 and test the conversion before I go and invest in 25 user licenses.

Why purchase 25 licenses? Use the Developers Edition to create
runtimes and purchase only licenses for your power users who create
queries and such to analyze data.

Microsoft Access (Office) Developer Edition FAQ
http://www.granite.ab.ca/access/developereditionfaq.htm

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