Errors trying to import a UserForm

Question

I am running Access 2007 SP3

When I export a UserForum from one database and attempt to import it into a second, I get an error saying “Errors during load.  Refer to xxxxxxx.log for details”.  Immediately afterwards I get a second error message “System Error &H80004005 (-2147467159).  Unspecified error” and then a third error “Out of Memory”.  The log file contains: “Line 2: Property OleObjectBlob in xxxxxxxxx could not be set.”

This also happens if simply drag and drop the UserForm from one database to the other.

This happens whether or not the UserForm has any controls on it.

This happens whether or not the receiving database has any UserForm in it (having an existing UserForum in the database would cause it to load references such as MSCOMCTL.OCX to support it).

If I create a new database and use the “External data” / “Import” function, all objects, excluding my UserForms are imported.

Does anyone have a clue what the problem is?

FoggArea

 

Answer 1

Is this perhaps another side effect of the recent problems with mscomctl.ocx? Search this forum for it.

---

-Tom. Microsoft Access MVP

Answer 2

Or check the solution FMS has at http://www.fmsinc.com/microsoftaccess/controls/mscomctl/index.htm

---

Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/djsteele (no e-mails, please!)
Co-author Access Solutions — Tips, Tricks, and Secrets from Microsoft Access MVPs (ISBN 978-0-470-59168-0)

Answer 3

Thank you for your suggestions, however I am pretty sure that is not the issue:

1) The date on my MSCOMCTL.OCX is 2005.  The date on system that I had previously fixed was 6/2012

2) The error occurs even when there are no controls on the form. On the machine that had that problem, well I found the problem by repeatedly deleting form then controls on a particular form to find out that it was ProgressBar 6.0 that was causing the problem

Despite this, I unregistered it and registered.

The problem remains.

2 other facts.

1) I found this problem during the early stags of trying to figure out the problem which turn out to be the MSCOMCTL.OCX problem, on a different computer.

2) This problem exist on both computer that I have tried it on.

Has any tried do this (moving UserForm from one database to another) on a Win 7 / Office 2007 machine, lately?

Thanks, and still confounded

Wayne

Answer 4

Hi Wayne,

>> When I export a UserForm from one database and attempt to import it into a second.

Are the two databases on the same computer or not? If they are on the different computer, could you try to built a userform on the second database from scratch? If it works Ok, I guess the MSCOMCTL.OCX files are different versions.

Regards,

Answer 5

The databases were/are on the same computer.

This is happening in both an existing, functional database and 2 brand new empty databases except one has a UserForm.

Again, one of the UserForms was empty of all controls so it is doubtful that MSCOMCTL.OCX would have been referenced by one of the controls since there are none.

Are you able do it (copy from one database to another) on any of your computers, lately?

Thanks Wayne

Answer 6

Hi FoggArea,

Welcome to the MSDN forum.

I am able to drag a form from one database to another and it is also OK to export a form to another database.

Regarding the behavior in the original post, I will try to involve some senior engineers into it. Your patience will be greatly appreciated.

Have a nice day.

---

Yoyo Jiang[MSFT]
MSDN Community Support | Feedback to us

Answer 7

Hi FoggArea,

There is now a "Fix It" utility available that corrects some of the recent issues with mscomctl.ocx.  Here is a link to the utility for Office 2007:

http://support.microsoft.com/kb/2687441

For the benefit of others, here are the links the 2003 and 2010 articles as well:

Office 2010:  http://support.microsoft.com/kb/2597986
Office 2003:  http://support.microsoft.com/kb/2687323

I hope this helps!

---

Sharon M, Microsoft Online Community Support

Answer 8

Sharon, Thank you for responding to my post. 

If you look at my previous replies you will notice that 1) I am well acquainted with the MSCOMCTL.ocx issue, 2) have good reason for believing that it is not my problem and 3) I've already applied the fix (whit no effect).

So... What else can we look at.

Doesn't UserFoms support live in FM20.dll, What is the latest version of FM20.dll?  What is the version of FM20.dll of a  machine that could import a UserForm.

HELP!!!!!!!

Wayne

Answer 9

Hi Wayne,

I looked into this further and it looks like you're actually running into a bug specific to the .ACCDB file format in Access 2007.  I wasn't able to reproduce the problem in Access 2010, but I was able to with Access 2007.  I can export a userform in Access 2007 from either a .MDB or .ACCDB but I can only import it into a .MDB file.   I get the same errors you're seeing trying to import into a .ACCDB file.  After importing into the .MDB file, I was able to convert the database to a .ACCDB file without a problem.  I'm hoping this is something that can work for you as well.

---

Sharon M, Microsoft Online Community Support

Answer 10

Oh, so close!

But...

Both of my databases are *.mdb 's.

Could you point me to where you saw this bug report?

Thanks Wayne

Answer 11

Hi Wayne,

Sorry to hear that didn't help.  I couldn't find anywhere this was documented publically.  I'm not sure what else could be causing the problem.  My best suggestion is to get a Process Monitor log to see if you can narrow down where the problem is.  You can download Process Monitor from the following location:

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

The only other thing I can suggest is to open up a support case with us so we can investigate further.  Hopefully someone else in the community will have some suggestions as well.

---

Sharon M, Microsoft Online Community Support

Answer 12

A new wrinkle.  I found a computer that had Access 2003 (it was as a Windows 7 machine) and it imported it from the *.frm files and/or allowed me to drag and drop it into a new *.mdb file with absolutely not issues.

I is starting to look like a Access 2007 bug.

Thanks Wayne.