I have a database that was built using Office 97 version and would
like to update a more current platform. This program runs on a server
and the enduser runs the program from thier desktop. Windows NT
setup. When updating the end users with Office 2003 and they
connected to the server database...many errors occurred. I reverted
them back to the 97 version and everything is fine.

What are some of the things that I would need to look at to upgrade
the database to a newer Office platform? Currently, the database
works fine but I think it would perform better on the new platform.

Any help on this would be great.

When you say your car don't work, or don't start, that is not much to go on.

In this case you are having problems with access. You not given a very
descriptive explanation of your problem. The only approach here is to start
asking a series of troubleshooting questions.

In the case the car we'd ask is the batteries OK, and do the lights work? Is
their gas in the car etc.

I have converted some extremely complex and large the applications with in
excess of 160 forms, and in excess of 30,000 lines of VBA code. The
conversion from access 97 to access 2003 went without a hitch and NO
problems occured at all.

Since you've not stated what kind of problems, and more imporant you not
stated what you attemped troubleshooting wise, I can only give you "general"
suggestions.

here is a few:

I would check is before you attempt to convert the access 97 application to
access 2003, you need to ensure that the application compiles correctly
*with* access 97. you can simply try compiling the code, or even attempt to
create a mde.

If the code compiles an access 97, then do a compact and repair, and then
try converting it to access 2003. once you've converted the application to
access 2003, then again you'll try to do a compact and repair, and then
yield to attempt to compile the code and see if any syntax and coding errors
have occurred during the conversion. if the application runs correctly, then
at that point you can create a mde, and distribute that to the users
workstations. Of course creating the mde assumes you split your application.

So, First and foremost for any application that is going to be multi-user,
will need to split the application. If you can't get this concept into the
head of your developers and the people you work with, then I suggest you
simply fire them, or leave the IT industry altogether and go back to paper
and pencil. I explain why you split your application here, and not only tell
you, I explain why you want to split your application:

http://www.members.shaw.ca/AlbertKal...plit/index.htm

The above is a general approach to the few things you would check. Since
you've not given any ideas as to the error messages or what you or your
design team of technical developers and support people have attempted so far
in the troubleshooting process, the above is only a starting point here...

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal (AT) msn (DOT) com

"buz" <internetranking (AT) hotmail (DOT) com> wrote

What gave you the idea that it "would perform better" on the new platform?

A cardinal rule for experienced developers is "Don't fix what ain't broke"
and a corollary, "Don't dink with working code."

For your information, Access 97 with its two Service Releases, is generally
acknowledged to be (at least arguably) the best-ever release of Access,
solid and stable.

But, if you are Hell-bent on trying to prove that "newer is better",
searching the newsgroup archives would be a good start, or using your
favorite search engine, and, especially, visiting MVP Allen Browne's site
(the link to which you can find in the Resource Links at my SharePoint site,
http://sp.ntpcug.org/accesssig/default.aspx, where he lists known bugs.

To get help here, you'll do much better if you can identify a specific
problem and give us reasonable details in a precise and concise question.
For other good suggestions on effective use of newsgroups, see the FAQ at
http://www.mvps.org/access/netiquette.htm.

Larry Linson
Microsoft Office Access mVP

On Mar 7, 1:41 pm, buz <internetrank... (AT) hotmail (DOT) com> wrote:

Often we find that that new stripper isn't nearly as much fun as our
old regular, but not before we waste money and time, and experience
disappointment.