By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,491 Members | 858 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,491 IT Pros & Developers. It's quick & easy.

Migrating Access 97 mdb to Access 2000

P: n/a
I've been given the task to migrate some existing MS Access mdb's from
97 to 2000 .

This exercise will include converting all table forms and code
modules.

I'm aware in Access 2000 you there is a menu command to covert to 2000

Have anyone migrated from 97 to 2000 before and if so I would be
grateful if you could post any problems / share any experiences on
this subject to start a discussion.

Also if anyone is aware of any functions that are obsolete in 2000 I'd
be grateful.

Thanks in anticipation

Chris
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
For each database:

Make sure it compiles without errors in A97.
Convert it.

(With a bit of luck that's the whole thing.)

Test it.

If you have used any third part addons to your A97 apps then you may have
to get updated versions of those.

Sometimes, it seems that the converted app fails because the library
references are incorrectly set. If you get stupid compilation or run-time
errors in the converted app then examine Tools>references with any module
open in design view. You should remove any reference to ActiveXDataObjects
2.n and ensure that you have a reference to DAO 3.6.

(Note that for new databases in A2000 the DAO reference is omitted and the
ADO reference is included. If you are continuing to use DAO then you need
to fix this for each new database.).

You definitely need the latest patches for Office2000. But if you have
any Access apps that send mail via Outlook be prepared to be p...d off.

Regards

Peter Russell

Chris Parker previously wrote:
I've been given the task to migrate some existing MS Access mdb's from
97 to 2000 .

This exercise will include converting all table forms and code
modules.

I'm aware in Access 2000 you there is a menu command to covert to 2000

Have anyone migrated from 97 to 2000 before and if so I would be
grateful if you could post any problems / share any experiences on
this subject to start a discussion.

Also if anyone is aware of any functions that are obsolete in 2000 I'd
be grateful.

Thanks in anticipation

Chris


Nov 12 '05 #2

P: n/a

Peter Russell <ru***@127.0.0.1> wrote in message
news:me***********************@russellscott.btinte rnet.com...
Snip>
You definitely need the latest patches for Office2000. But if you have
any Access apps that send mail via Outlook be prepared to be p...d off.
What do you mean on this Peter.
I`ve put one of my apps onto O2000 and the mail via Outlook routine is coming
up with -91 object variable or with block variable not set - message.
References all have been double checked to no avail
David B

Regards

Peter Russell

Chris Parker previously wrote:
I've been given the task to migrate some existing MS Access mdb's from
97 to 2000 .

This exercise will include converting all table forms and code
modules.

I'm aware in Access 2000 you there is a menu command to covert to 2000

Have anyone migrated from 97 to 2000 before and if so I would be
grateful if you could post any problems / share any experiences on
this subject to start a discussion.

Also if anyone is aware of any functions that are obsolete in 2000 I'd
be grateful.

Thanks in anticipation

Chris


Nov 12 '05 #3

P: n/a
David B previously wrote:
You definitely need the latest patches for Office2000. But if you
have
any Access apps that send mail via Outlook be prepared to be p...d
off.


What do you mean on this Peter.
I`ve put one of my apps onto O2000 and the mail via Outlook routine is
coming
up with -91 object variable or with block variable not set - message.
References all have been double checked to no avail
David B


The specific issue I was referring to is the increased security
implemented in Off2000 Sp2 (?3 , I forget which) that forces you to
acknowledge every email issued via automation. It's not that anything
will stop working.

Your situation looks like a coding issue, so your best bet to get help (if
you want any) is to create a new thread here and post the problem code.

Regards

Peter Russell
Nov 12 '05 #4

P: n/a
I recently converted from 97 to 2000 and it was a nightmare. Many of the
reports were not correct or would not display at all. I was so mad I wanted to
revert back to 97. After talking to Microsoft (in India) for an hour an a half
they came to the conclusion that the convert process was not working correctly.
The solution was to IMPORT into 2000 all tables, querys, forms, reports, etc..
That seems to take care of the conversion problem. However, 2000 still acts
strange and I wish I could have kept 97.
Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.