Transfer an existing database on a new PC

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

What should be done to properly transfer a secured FE database to a new PC?
There will be a change in the operating system from Win 2000 Prof. to XP
prof. and Access will be the same Access 2000. How do I verify if my
original developement computer has the same identical version of Access 2000
with the new target computer? Target computer had latest updates downloaded
to Access 2000. Original computer with development database may not have had
the most recent updates applied to Access 2000. Is this a critical
requirement to a successful transfer and fully operational database? What is
the best way to verify this if it is a critical step?
 
Since the References collection is very sensitive to version differences,
and since the updates may have impacted a referenced library, the fact that
the target computer and the development computer are different might make a
difference. Once you've transferred the application(s), go into the VB
Editor and compile the application (it's under the Debug menu). That should
highlight any issues with References problems.

If you do appear to have a References problem, open any code module, select
Tools | References from the menu bar and examine all of the selected
references (they'll all be at the top of the list)

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

Of course, if your application is using any other than the basic references,
you'll have to ensure that the additional references exist on the new
computer.
 
Doug,

Thank you very much! It worked. I've been stuck without design change
control for weeks now. I have no modules but created a new just to open VB.
I followed your instructions and found one reference with "Missing" word so I
unchecked it and had to re-run compile again to verify it would run with no
error. It did. I tried to create an MDE and Access forced me to save or not
the module changes so I did. I'm now able to create an MDE and was not able
to before. Thanks again!
 
Back
Top