Hello! I have gotten so much help from this board and I do not feel the greatest where my first contribution is in the form of another question/problem, but now that I am here, who know!?
I will try and keep it short. I have built an Excel-based scheduling tool with a custom ribbon in a shared workbook. I have also customized RoryA's ribbon ID bit to accommodate 50 users simultaneously and everything has been working nearly flawlessly, except:
When the shared workbook was last saved with Excel window maximized and the next user has Excel running in normal window mode, opening the file causes Excel to attempt to maximize the window which then returns the "429 - ActiveX component can't create object" error before any code is run. It seems as the maximization of the application window process prevents the creation of the ribbon and this occurs before any code is run.
I have added a workaround to BeforeSave to store each user's window state, change application.windowstate to normal, save, then restore user's previous window state, but have not been able to fix this problem.
Has anyone experienced this strange behaviour? Any thought/idea/guess/pointer is greatly appreciated!
BTW, the spreadsheet works without any issue when in single-user mode.
I will try and keep it short. I have built an Excel-based scheduling tool with a custom ribbon in a shared workbook. I have also customized RoryA's ribbon ID bit to accommodate 50 users simultaneously and everything has been working nearly flawlessly, except:
When the shared workbook was last saved with Excel window maximized and the next user has Excel running in normal window mode, opening the file causes Excel to attempt to maximize the window which then returns the "429 - ActiveX component can't create object" error before any code is run. It seems as the maximization of the application window process prevents the creation of the ribbon and this occurs before any code is run.
I have added a workaround to BeforeSave to store each user's window state, change application.windowstate to normal, save, then restore user's previous window state, but have not been able to fix this problem.
Has anyone experienced this strange behaviour? Any thought/idea/guess/pointer is greatly appreciated!
BTW, the spreadsheet works without any issue when in single-user mode.
