Upsizing access 97 app

[John]

Hi

I need to upsize an access 97 app to sql server. Is it possible to upsize is
directly or should I first upgrade the app to access 2003 before upsizing?
Is there an upsizing wizard for access 97?

Thanks

Regards

 

[Larry Linson]

There _was_ an upsizing wizard for Access 97. It may still be available. If
I were going to convert an Access 97 database to client to SQL Server, I'd
look for it, because it would set up Access <-> Jet <-> ODBC <->SQL Server
which is once again the configuration recommended by the Microsoft insiders.

You can set up such a configuration with Access 2003, but not with the
"Upsizing Wizard" which was created while they were still believing their
own hype about ADPs.

That said, if you have someone on staff reasonably experenced with SQL
Server, they could quickly re-create most Access table structures, then you
could simply link the tables or stored procedures and begin modifying the
Access client -- and don't, for a minute, believe that you won't need to do
some mods for performance.

A good Access single-user application, just converted, does not a good
Access multi-user application make, and neither, just upsized, does a good
client-server application make.

Look in http://appdevissues.tripods.com/downloads.htm for a presentation on
Access in the client-server environment that I did for my user group, some
time ago.

Larry Linson
Microsoft Access MVP

 

[John]

The page cannot be displayed???

There _was_ an upsizing wizard for Access 97. It may still be available.
If I were going to convert an Access 97 database to client to SQL Server,
I'd look for it, because it would set up Access <-> Jet <-> ODBC <->SQL
Server which is once again the configuration recommended by the Microsoft
insiders.

You can set up such a configuration with Access 2003, but not with the
"Upsizing Wizard" which was created while they were still believing their
own hype about ADPs.

That said, if you have someone on staff reasonably experenced with SQL
Server, they could quickly re-create most Access table structures, then
you could simply link the tables or stored procedures and begin modifying
the Access client -- and don't, for a minute, believe that you won't need
to do some mods for performance.

A good Access single-user application, just converted, does not a good
Access multi-user application make, and neither, just upsized, does a good
client-server application make.

Look in http://appdevissues.tripods.com/downloads.htm for a presentation
on Access in the client-server environment that I did for my user group,
some time ago.

Larry Linson
Microsoft Access MVP

 

[Sylvain Lafontaine]

Remove the letter s after tripod.

 

[Larry Linson]

Remove the letter s after tripod.

Mea culpa -- I typed it in instead of copy/paste.

Larry

 

[david epsom dot com dot au]

If you intend to use A2003 as the interface, you should
upgrade to 2003 before upsizing.

If you intend to use A97 as the interface, you can't use
the 2003 wizard because it creates nChar fields (National
char, that is, unicode) fields, which are incompatible
with A97. (Or you can use the wizard and then go through
all your tables changing the field type for all text fields).

The A97 wizard is or was available in source form (with
the .MDE extension, but don't let that fool you), so that
you can correct it so that it works with current versions
of SQL Server. It will NOT work unless it is corrected:
the version number jump from 7.0 to 2000 broke the wizard.
The problem is easy to fix: you just turn on 'break on
all errors' and fix the problem where it occurs.

If you can't find or won't fix the A97 wizard, you can
use SQL DTS to import the tables: I think you will need
to fix up relationships after import.

(david)