Exporting a form

[Guest]

When I export a form from one access application to another the changes I
made in the form I am exporting do not come over.

Even when I delete the form from the 2nd application and re-import the form
from the 1st application, the form comes over but it reflects the Old form
without the changes.

How can this be happening and how can I resolve this?

 

[Granny Spitz via AccessMonster.com]

Even when I delete the form from the 2nd application and re-import the form
from the 1st application, the form comes over but it reflects the Old form
without the changes.

Open the 2nd app and import the form. If the form in the 1st app is named
frmInvoices and you already have a form by that name in the 2nd app, look for
frmInvoices1 in the 2nd app.

 

[Guest]

I imported the form and the same thing happened as when I exported the form.

In the 1st application, I added a button and some code to the revised form.
When I either import the form or export it, the form coming over does not
have the changes (the new button and code). What would cause this to happen?

The form that comes over looks like the old form before the changes.

 

[Granny Spitz via AccessMonster.com]

In the 1st application, I added a button and some code to the revised form.

This is a *major* change to an object. Major changes won't save unless you
have exclusive access to the file when saving the object. Is this a
multiuser database shared on the network? It should be split, with the back
end (tables, relationships) on the network and a copy of the front end
(queries, forms, etc.) on each user's computer.

 

[Guest]

It is a database on my laptop and the application is split from the tables.

 

[Larry Linson]

It is a database on my laptop and the application is split from the
tables.

Had you closed the form in design view before exporting or importing it?

Do the changes show in the database in which they were made?

This seems more than a little "unusual."

Larry Linson
Microsoft Access MVP

 

[Guest]

Yes I believe that I have typically closed the design view before importing
it and yes the changes do show up in application #1 but not in the
application that I am importing them to.

It has worked for every other form I either imported or exported except for
this one.

I thought it might have to do with permissions so I made sure they were full.

 

[Larry Linson]

Yes I believe that I have typically closed the design view
before importing it and yes the changes do show up in
application #1 but not in the application that I am
importing them to.

It has worked for every other form I either imported or
exported except for this one.

I thought it might have to do with permissions so I
made sure they were full.

Specifically, how are you importing / exporting the Form... manually with
File | Get External Data, or code (if so, what code)? Have you tried
CopyObject in code -- that has always been a rock-solid approach for me --
well, after Access 2.0, which had the infamous CopyObject Flaw that did make
it easy to get a copy of everything but the data from the DB.

I'm at a loss, since I haven't experienced anything similar.

Just as "an exercise," copy your DB, and Compact/Repair the original, then
try import/export.

Larry Linson
Microsoft Access MVP

Larry Linson
Microsoft Access MVP

 

[Guest]

I did as you suggested and compacted and repaired the database.
Unfortunately it did help when I tried to re-export the form.

Since it was much more work just trying to figure out why this one form
would not import, I just recreated it in application #2.

Thanks for your help. I don't understand why the import/export has worked