Re: Converting Access 97 MDE to Access 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hello, and thank you for your replies. I have finally had a chance to
start on this conversion and I ran into a compile error, BUT I think I
approached this incorrectly.

Here's a review of our situation:

1. We used Office Developer ODE Tools 97 to create a custom database
program back in 2002. This created an MDB & MDE and we used the Setup
wizard to create the setup floppies to install on our customer's
computer. (We distributed this as an Access Runtime).
2. Our customer upgraded to a new computer running Windows XP with
Access 2003. The first error they had upon opening the program (they
had copied the MDB from the old computer) was related to "Missing or
broken reference to file 'dao2535.tlb' version 3.5'
3. We still have Office Developer ODE Tools 97 on an old laptop. We
also have the original MDB we created for the customer.
4. We also have Office Developer XP (2002) Tools running on XP Pro.
5. We also have VirtualPC2004 to run Office 2003 in order to emulate
our customer's setup.
6. We have the customer's file with their data they have added since we
distributed it to them.

Please outline the steps we should take in order to convert our
customer's current MDB (in Access97 format) to Access 2003.

My immediate question is whether I will need to use my old 97 Developer
tools in this conversion process?

Thank you

.



Relevant Pages

  • Acc97conversion to a2003
    ... This created an MDB & MDE and we used the Setup ... We still have Office Developer ODE Tools 97 on an old laptop. ... also have the original MDB we created for the customer. ...
    (microsoft.public.access.conversion)
  • Re: Acc97conversion to a2003
    ... > wizard to create the installation floppies to install on our customer's ... We still have Office Developer ODE Tools 97 on an old laptop. ...
    (microsoft.public.access.conversion)