I am working on a macro addition of Word VBA for 80 or so users. The office has a high staff turnover, so the training suffers, and therefore one of the requirements for itself for this project is full and friendly documentation. However, to complement this, and to save newbies to open a 100-page document when they want to try something new, I need a status bar for each user form (there are five of them), which provides contextual help. I find the tips annoying.
I do not have much experience, so I wanted
Essentially, I have a file containing all the status lines. (This is currently a text file, but I was wondering if I should use a spreadsheet or csv to make editing easier for other staff in the future.) Each control has a MouseMove event that refers to a function: getStatus (cID) that opens the file captures the line and displays it in the status label. It also captures several parameters from the same line in the file, for example, whether it is possible to click a label (to link to a page in the help file) and what color the label should be.
So, actually a few questions arise:
Will the application be slow if the user form constantly refers to the file? I'm fine, but I've been doing this for too long, and I'm the only user who accesses this file. There will be 80 constantly turning to him.
Is MouseMove over a control a better way? Should I use coordinates instead?
The most important thing (from the point of view that I have to do as little work as possible) is there a way to do this so that I do not have a MouseMove event for each control? I have several hundred controls, each with its own identifier (well, not yet, but they will, if that's the only way to do this). Maybe when the form loads, I can load ALL possible status bars so that they are ready for when the control will be processed. But then, maybe the load time is negligible?
Appreciate any ideas or thoughts, especially if VBA already has a number of features to do this already, and I'm just trying to invent a wheel. I cannot use the application status bar because the user rarely sees the application directly.
Thanks!
EDIT:
, .
, - - , - :)