You ask, you get.
The problem is that I have a problem with a problem remote user who has reported a weird problem with a fairly complicated, VB-rich, spreadsheet I developed for his employing company.[ ] This employee works in a one-person office a thousand kilometres from his employer's head office, and I live across a large city from this headquarters.[ ] The head office USED to have a person who was IT-literate, but no longer.
They recently "updated" their file system to something that might (or might not) involve some combination of OneDrive, SharePoint, and (I think) something with a name like FileCentre.[ ] As a person who works alone, at home, with a simple stand-alone computer, I know nothing about any of these.[ ] And it seems neither do they.[ ] Every aspect of the spreadsheet works perfectly on my system.[ ] In normal times I would travel across town to their office, sit at one of their standard computers, and dig in.[ ] But the entire country (planet?) is in WuhanVirus-induced lockdown, so that is impossible.
Plan D is to create a simple spreadsheet that basically uses VBA to extract as much information as possible about the operating environment and report it to the remote user, for him to pass back to me.[ ] I send him that spreadsheet, get him to store it in exactly the same manner and location as the troublesome spreadsheet, then run it.
One aspect of the "operating environment" I am interested in is the way he is firing up the spreadsheet.[ ] Hence my starting post yesterday.
Why am I interested in this aspect, I hear you ask.[ ] Because a couple of years ago this company had another problem with the spreadsheet.[ ] I could not reproduce the problem.[ ] After a lot of too-ing and fro-ing I discovered that I was always starting the spreadsheet one way and they were always starting it the other way.[ ] The problem's occurrence depended on the starting method.[ ] Once I knew that, it was easily solved.
