If memory serves, beginning with Access 97 you can not push an object
such as a form from one database into another, even if you try to
delete it first. We used to do things that way back in the Access 2.0
days to distribute version updates to our users. In Access 97, you
have to drive the process from the file being updated. That is, in
the file to update, delete the existing object then pull the updated
copy from your update database. Since you obviously don't have the
hooks in place to automate the process, you will have to give your
users instructions to do it themselves. Send them an mdb with the
updated form and show them how to delete the existing form then use
File | Get External Data | Import, etc. to import the form. HTH
Rick Collard
www.msc-lims.com
On 17 Feb 2004 09:16:59 -0800,
mi****@msn.com (Michael Eisner) wrote:
I have an MS Access 8.0 (Office97) program that has a form called
FO-008 that I need to replace on several users computers in different
locations without me being there doing it manually.
I'm trying to perform the replacement by using an external MS Access
program that contains the replacement form also called FO-008. I need
to keep the same form name since the form contains relationships to
other forms and quarries in the program.
When I run the Macro (CopyObject ) I get the following error message
"Object Invalid or no longer set"
Macro Info:
Destination Database:
C:\00-Dell-Transfer\Testing\User-Mropuf20.test.mdb
New Name:
Source Object Type: Form
Source Object Name: FO-008
Can anyone help me?
Is there another way to do it?
