Loading a user form crashes Excel 2003 -- the second time it's opened

**Bob Eaton** · 12-23-2012, 05:41 PM

Hi. First post. Quite new to programming in Excel. Some experience in VB6. So here goes:

This seems like come kind of odd memory problem but I'm not sure where to look.

I have a fairly large workbook where I've added a user form with a bunch of controls.
The first time I load the file the user form opens fine. But the second time I load it (with Excel still running) the user form will crash Excel starting with a Path\Access file error.

I currently have any startup code in the workbook and user from commented out.
I do a show statement with a command button (I eventually want to auto load it.) and then unload the user form in the Workbook_Deactivate event.

I tried this on two machines with Excel 2003 and the results are the same.

However -- on a third machine running 2007 it seems to work just fine....

Any thoughts? Is there something else I should be doing to release memory? (Or is this a bug in 2003?)

Thanks for your help!
Bob

**Leith Ross** · 12-23-2012, 06:59 PM

Hello Bob,

Welcome to the Forum!

You should post your workbook for review. Without seeing the code, any suggestions would be guesswork. There were many changes made to Excel 2007 that don't work in 2003. Again, it would necessary to see the code to which, if any, calls are incompatible.

To Post Your Workbook

At the bottom right of the Reply window, Click the button Go Advanced
At the top of the Your Message Window, in the first row of icons, Click the Paperclip icon.
Click the Add Files button at the top right in the dialog box. This displays the File Manager dialog.
Click the Select Files button at the bottom middle of the dialog.
In the new window Find the file you want to upload, select it, and Click Open.
You will now be back in the File Manager dialog. Click the bottom Middle button Upload File.
Wait until the file has completely uploaded before you exit the File Manager dialog.

File Manger Pic

**Bob Eaton** · 12-23-2012, 07:19 PM

Thanks.
It contains proprietary info which is why I didn't post it initially.
I don't believe there is any code running but I could be wrong.
I'll try stripping out content and if it still crashes I can post it.
I thought I would see first if there were any known issues.