Migratation Access 97 to Access 2003

[Wayne]

Hello,

I am planning to migrate Access 97 to Access 2003, we have
around 20 live applications with forms, reports and
macros, I am scare right now due to enough knowledge, I
read many article at Microsoft but I didnt get right way
to migrate. If any one guide me how to accomplish my
project and what types of problem I will face during
migration. Any links and info. about it I really
appriciate for helping me.

Thanks in advance

 

[Mable]

You may want to consider doing a 'trial run,' by setting
up a machine ad hoc and installing access 2003 on it. YOu
can then bring over your databases (making sure to create
a LOCAL copy so that you won't screw up the originals) and
attempt to convert. If all goes well, then so should your
migration.

If not, let us know.

 

[Wayne]

Thanks for your prompt response, I have test machine I
converted to Northwind example data base to access 2003 it
seems ok I checked throughly I didnt get any problem with
that. when I copy my database I believe it doesnt work
properly, becz it is network application but I will try it
at local machine.

Thank you.

 

[Mable]

If it gives you trouble concerning networked applications,
you could always attempt it on a test machine hooked up to
the network; just make backups of all of the referenced
files. Make a copy, change the original's name
to .bak.mdb, and see how it works. If you come across
trouble, remove the test machine, delete the converted
files, and rename the originals back to their .mdb names.

(.mdb should be whatever the extension is for the files,
don't go changing all of them to .mdb because i said so :-
P)

 

[PatrickO]

Hi Wayne,

I am in the process of doing the same migration.

Something i ran into is referencing a fieldname in a recordset.

Dim MyRS1 As Recordset,

Set MyRS1 = MyDB.OpenRecordset("Table", DB_OPEN_TABLE) ' open recordset

MyRS1.Index = "PrimaryKey" ' set index for seek function
MyRS1.Seek "=", MyRS.TheField ' search for selected corresponding record

The MyRS.TheField should be replaced by MyRS!TheField

Greetings Patrick

 

[Vern]

Hi Patrick:

to clarify: your suggestion applies to DAO or ADO ?
which version ?
i am planning (hoping) to use DAO 3.6 even with
ACCESS'2003 by placing the reference higher in the
reference resolution order than any reference to ADO (thus
avoiding any unqualified references to common objects)

thoughts ?

thanks

Vern

-----Original Message-----
Hi Wayne,

I am in the process of doing the same migration.

Something i ran into is referencing a fieldname in a recordset.

Dim MyRS1 As Recordset,

Set MyRS1 = MyDB.OpenRecordset("Table",

DB_OPEN_TABLE) ' open recordset

 

[Tony Toews]

i am planning (hoping) to use DAO 3.6 even with
ACCESS'2003 by placing the reference higher in the
reference resolution order than any reference to ADO (thus
avoiding any unqualified references to common objects)

It's my understanding this works quite well. Although the purists
will likely urge you to disambiguate any ambiguous references this
could be quite a lot of work.

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

 

[PatrickO]

Hi Vern,

This refers when changing the reference from DAO 2.5/3.5 to DAO 3.6.

Greetings