The following code is supposed to open a form when the Excel package starts. It's located in "ThisWorkbook" module.
Instead, I get a Path/File access error message. Debug identifies the last line but freezes the program.
Please Login or Register to view this content.
What am I doing wrong? Do I need to include the full path to the form? If so, how is that done?
Thank you
If the name of the form is same as the one in the Form properties, this should work
Also, the first line,can be skipped too.Please Login or Register to view this content.
If this doesn't work attached the spreadsheet.
If you think someone helped you, click on the "* Add Reputation" as a way to say thank you.
If your problem is solved, go to Thread Tools and select Mark This Thread Solved
The name is the same. I thought it should work, too! I'm afraid I can't attach the workbook, too big and too sensitive. Maybe I need to load the form first?
You can remove the sensitive information & then upload the workbook, if you wish to do so. (SEE THE YELLOW RIBBON ABOVE FOR INSTRUCTIONS)
I tried the code on a simple form and it worked properly.
I'm so sorry I can't upload the workbook. There are 19 modules and as many sheets plus three forms. The command to show the form is so basic, the problem probably lies in the order of calling.
I have not used a "Load" command nor any "initialize" anywhere but I have one activation procedure which is in the code of the form, not in a separate module.
The code within the activation is not included here because it isn't an issue.Please Login or Register to view this content.
The form shows up fine once the package is loaded. I can call it up with a key combination. It's just in ThisWorkbook that it fails.
So, two questions:
1. When Excel opens, does it need a "Load Form" first or is that used only if more than one instance of the form is needed?
2. Do I need an initialize procedure for the form or is the activation sufficient?
Thanks.
Can you post the userform code?
Click the * Add Reputation below to say thanks.
Try moving the code that shows the form to a routine in a normal module like this:
then amend the Workbook_Open code to this:Please Login or Register to view this content.
Please Login or Register to view this content.
Everyone who confuses correlation and causation ends up dead.
The userform code is a series of simple procedures connected to buttons. They aren't the problem.
If I put almost anything in the Workbook_Open() procedure, the whole package crashes. For example:
causes and Automation error and major malfunction.Please Login or Register to view this content.
Someone suggested cleaning the entire pacakge, and I may try that.
Okay, I will try this very soon. Thank you. (In reply to RoryA)
I have tried this now but no luck - received Automation Error and complete system meltdown.
I'm not sure this thread can be resolved here. I think there is some bloating and serious cause for concern deep within my package which needs attention, perhaps some VBA / XML cleaning.
I may do a complete export and import of modules - again.
Thanks for your ideas - in normal circumstances they should work.
Last edited by insomniac53; 12-04-2019 at 08:28 AM.
Is your file in a cloud storage?
Good point. Yes and no - I was using OneDrive but it was giving me so much grief I moved my work to sync with Dropbox - but the actual Excel file is on the hard drive, on top of the Dropbox folder. I will try something - I'll make a copy onto a drive area that does not sync and see if that works. Thanks for the idea.Originally Posted by dotchiejack
Well well! I tried the package without the sync and it worked like magic. I need to test it over a longer period, but if this is the issue, I don't understand why. Never mind, thank you so much for the suggestion.
Glad it worked.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Register To Reply
Bookmarks