A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.
I received a copy of the OP's project and have emailed a reply to him and the problem has been resolved satisfactorily.
The following information is for anyone else experiencing a similar problem and demonstrates that some VBA errors such as stopping on a simple line of code like selecting a worksheet are not necessarily due to a problem with the worksheet and can be due entirely to something else.
It was established that attempting to select other worksheets resulted in the same problem and therefore needed to look further than the worksheets.
There were 21 Userforms in the project. Firstly all the Userforms were exported and then removed from the project and then code re-compiled. (This entailed commenting out some code to Show the Userforms.)
Testing indicated that the problem no longer existed. Therefore each Userform was imported one at a time, the code re-compiled and retested. Two problem Userforms were identified and both of these were identical and the OP was able to confirm that one was obsolete so it was left out.
The properties of the problem Userform were recorded by opening the properties for the Userform plus each control separately and using the Snipping tool to record the exact properties. The Userform was then re-created from scratch and the remaining Userforms imported.
Initially the problem appeared to be resolved. However, the OP identified that one TextBox control had been omitted from the new Userform. It was missed because the BackStyle property was Transparent and it did not contain a value and hense was not obvious to me. (A lesson here is to use the drop down at the top of the properties dialog to identify and select each control instead of with properties dialog open and selecting each control on the Userform.) When the TextBox control was re-created, the problem returned.
The TextBox control had a ControlSource so that was removed and the problem disappeared again. Therefore it was narrowed down to the ControlSource of the TextBox. Due to the complexity of the entire project and protect and unprotect code throughout the entire VBA code rather than in a called sub, it was too difficult to totally test but I think that it was due to the ControlSource cell being protected at the time of opening the project. Therefore I tested in a stand alone workbook with just a copy of the Userform and some code in the Workbook Open event but this did not cause a problem during opening the workbook; only when the Userform was opened and if the value in the TextBox was changed.
The final solution was a work around. Remove the ControlSource property from the control and insert code in the Userform Initialize event to re-establish the property and in the Userform Deactivate event to remove the ControlSource property. With this done the entire problem was resolved.
Because I have not been able to emulate the problem in a stand alone workbook with a copy of the Userform, it is still not beyond the possibility that some other form of corruption is in the workbook and it is this that is interfering with the ControlSource property.