MrRhodes2004
11-01-2016, 04:19 AM
Hey Group,
It has been a while for me to post here and I have always received excellent help.
I am in the process of writing a "tool" that significantly manipulates application and workbook settings. I am using Full Screen and removing all standard Excel options then providing my own buttons for navigation. For the most part, it will works well (enough). The coding is ugly as sin though.
I am about to send the tool out for alpha testing. The first couple of user crashes left the application in the modified state. There was literally nothing available to the user except the worksheet with gridlines. Since the user have no clue about excel, they were completely stuck. Lucky I was there to be able to reset what had been done and develop a fix. But that was just one user.
I am looking for a way to use a new, blank workbook that records all of the states of excel. For example, below are some of the states that I would like to capture and save to the workbook:
ActiveSheet.Calculate
ActiveWindow.DisplayHeadings
ActiveWindow.DisplayGridlines
ActiveWindow.DisplayHorizontalScrollBar
ActiveWindow.View
ActiveWindow.Zoom
ActiveWindow.DisplayWorkbookTabs
Application.DisplayFormulaBar
Application.ScreenUpdating
Application.WindowState
The idea is that the user would open this RescueWorkbook.xlsm prior to working with my "tool". It would record their settings..."just in case". If the tool caused a problem, they could reopen the RescueWorkbook and it could reset all of the original values.
Is there an easy way to do this? I also don't want to miss elements of the application that are inadvertently or unintentionally changed.
Thoughts? Ideas?
Michael
PS. Are there brave souls who would be willing to test the "Technical" aspects of the "tool"? No understanding of the material required but be able to read and following instructions, click buttons, try to do different things, essentially try to break the tool so that I can attempt to fix the "bugs" before it goes live? It is for my master thesis and I defend in January.... and I would rather it not "Break" during the defense.
It has been a while for me to post here and I have always received excellent help.
I am in the process of writing a "tool" that significantly manipulates application and workbook settings. I am using Full Screen and removing all standard Excel options then providing my own buttons for navigation. For the most part, it will works well (enough). The coding is ugly as sin though.
I am about to send the tool out for alpha testing. The first couple of user crashes left the application in the modified state. There was literally nothing available to the user except the worksheet with gridlines. Since the user have no clue about excel, they were completely stuck. Lucky I was there to be able to reset what had been done and develop a fix. But that was just one user.
I am looking for a way to use a new, blank workbook that records all of the states of excel. For example, below are some of the states that I would like to capture and save to the workbook:
ActiveSheet.Calculate
ActiveWindow.DisplayHeadings
ActiveWindow.DisplayGridlines
ActiveWindow.DisplayHorizontalScrollBar
ActiveWindow.View
ActiveWindow.Zoom
ActiveWindow.DisplayWorkbookTabs
Application.DisplayFormulaBar
Application.ScreenUpdating
Application.WindowState
The idea is that the user would open this RescueWorkbook.xlsm prior to working with my "tool". It would record their settings..."just in case". If the tool caused a problem, they could reopen the RescueWorkbook and it could reset all of the original values.
Is there an easy way to do this? I also don't want to miss elements of the application that are inadvertently or unintentionally changed.
Thoughts? Ideas?
Michael
PS. Are there brave souls who would be willing to test the "Technical" aspects of the "tool"? No understanding of the material required but be able to read and following instructions, click buttons, try to do different things, essentially try to break the tool so that I can attempt to fix the "bugs" before it goes live? It is for my master thesis and I defend in January.... and I would rather it not "Break" during the defense.