JohnPablo
asked on
Excel 2013 SDI, modal User Forms and multi-workbook.
Hi Experts,
I'm having a problem with my VBA app an all Office 2013 computers. When they run some procedures, they get strange errors no one gets in pre-2013 versions. This is the most urgent I'm dealing with now:
Workbook1 is open. Procedure_A calls userform_A which creates a Workbook2 filling it with calculations from Workbook1. When both are finished, Workbook2 is active but its ribbon is frozen, blank. If I switch back to Workbook1, its ribbon is visible and functional. The only way to close workbook2 is by right-clicking on the task bar. This does not happen on Excel 2010.
I know this is happening because SDI doesn't work well with modal user forms, but it would be a pain in the neck to rewrite several parts of my code just to go modeless, not to mention finding ways to prevent users from ruining everything by clicking on the background while the user form is still active.
Is there any work around this?
Thanks,
Pablo.
I'm having a problem with my VBA app an all Office 2013 computers. When they run some procedures, they get strange errors no one gets in pre-2013 versions. This is the most urgent I'm dealing with now:
Workbook1 is open. Procedure_A calls userform_A which creates a Workbook2 filling it with calculations from Workbook1. When both are finished, Workbook2 is active but its ribbon is frozen, blank. If I switch back to Workbook1, its ribbon is visible and functional. The only way to close workbook2 is by right-clicking on the task bar. This does not happen on Excel 2010.
I know this is happening because SDI doesn't work well with modal user forms, but it would be a pain in the neck to rewrite several parts of my code just to go modeless, not to mention finding ways to prevent users from ruining everything by clicking on the background while the user form is still active.
Is there any work around this?
Thanks,
Pablo.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
![Avatar of [ fanpages ]](https://filedb.experts-exchange.com/files/public/2020/2/28/4acbe344-900b-4e79-96ce-65fe58a6f004.png){kind=small}
Are you still working on this, Pablo?
ASKER
I've requested that this question be deleted for the following reason:
It didn't raise enough interest.
It didn't raise enough interest.
---
Delete Request Pending
JohnPablo requested that this question be deleted for the following reason:
It didn't raise enough interest.
To cancel this request and generate a request for Moderator review, state your reason for objecting in the standard comment box and click the 'Object' button. This question will be closed on 7/22/2015 if there are no objections.
---
Objection: The question asker is opting to delete a thread without providing feedback on an ongoing solution.
Delete Request Pending
JohnPablo requested that this question be deleted for the following reason:
It didn't raise enough interest.
To cancel this request and generate a request for Moderator review, state your reason for objecting in the standard comment box and click the 'Object' button. This question will be closed on 7/22/2015 if there are no objections.
---
Objection: The question asker is opting to delete a thread without providing feedback on an ongoing solution.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
ASKER
It makes a lot of sense. One quite obvious way I found to fix it was moving the code that added the new workbook out of the user form. Since I have a number of procedures that work this way, moving the code or going modeless is not always an easy fix; but closing the new file, closing the user form, and then reopening the file seems like a viable option.
I'll let you know how it goes.