From: David W. Fenton on 5 Feb 2010 20:02 "Tony Toews [MVP]" <ttoews(a)telusplanet.net> wrote in news:kcnnm5di776eojvik9pn5vii0cfevamg5j(a)4ax.com: > If the user is not a "master" workstation, and you/they click on > the StartMDB.exe it brings up the same screen showing all the > configuration files that the "master" user gets. However the only > option visible is to choose which configuration file to execute. > None of the other command buttons will be visible or selectable. > And no menu options will be visible either. > > IOW al the user can run is "Run Configuration File." That sounds foolproof, too, and solves the problem you were trying to solve with the other approach, but enhances ease of use for eveybody involved. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
From: David W. Fenton on 5 Feb 2010 20:04 "Tony Toews [MVP]" <ttoews(a)telusplanet.net> wrote in news:fpnnm5ds66fhdh87bclilm8ej2d76ifecn(a)4ax.com: > "Tony Toews [MVP]" <ttoews(a)telusplanet.net> wrote: > >>>But I'm setting up the workstations for them, so I'm going from >>>machine to machine running the utility to get the shortcut on the >>>desktop. If I could get the wizard to run, I could select the INI >>>file and run it to create the desktop shortcut. >> >>I'll change the logic so that: >> >>If the user is not a "master" workstation, and you/they click on >>the StartMDB.exe it brings up the same screen showing all the >>configuration files that the "master" user gets. However the only >>option visible is to choose which configuration file to execute. >>None of the other command buttons will be visible or selectable. >>And no menu options will be visible either. >> >>IOW al the user can run is "Run Configuration File." > > Make that "IOW all the user .." What, you're going to prevent users named Al from running it? > BTW thanks for pointing this out. I've never liked that > unfriendly message telling the user "Null command line." But I've > never been able to figure out a good means of replacing it. And > now I have with your help. I think error messages should be simple and to the point. If more detail is desired, the message should point to it, but any error dialog should provide possible solutions to the problem (if appropriate and feasible). > Well, with one exception. The exception being the case where an > AutoFEUpdater.INI file exists, this user/ workstation isn't in it > and there are no configuration files. Oh well. That makes sense, too. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
From: Tony Toews [MVP] on 6 Feb 2010 01:44 "David W. Fenton" <XXXusenet(a)dfenton.com.invalid> wrote: >> Thanks very much for explaining in detail what you were expecting >> and your situation! > >This is why I hate creating user documentation (pace a >Stackoverflow.com thread on that topic that you've contributed to), >because I don't know what needs to be explained. One thing I've found about the Auto FE Updater is I get next to no feedback about what works and doesn't work. So I'm exceedingly grateful for postings like yours where we can discuss the issues and so I can understand what you are doing. And I agree with you about creating user docs. I hate that too. Every time I get an email I try to update the website and create an FAQ. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/
From: Tony Toews [MVP] on 6 Feb 2010 01:45 "David W. Fenton" <XXXusenet(a)dfenton.com.invalid> wrote: >>>IOW al the user can run is "Run Configuration File." >> >> Make that "IOW all the user .." > >What, you're going to prevent users named Al from running it? <whack> Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/
From: Tony Toews [MVP] on 6 Feb 2010 01:47
"David W. Fenton" <XXXusenet(a)dfenton.com.invalid> wrote: >> If the user is not a "master" workstation, and you/they click on >> the StartMDB.exe it brings up the same screen showing all the >> configuration files that the "master" user gets. However the only >> option visible is to choose which configuration file to execute. >> None of the other command buttons will be visible or selectable. >> And no menu options will be visible either. >> >> IOW al the user can run is "Run Configuration File." > >That sounds foolproof, too, and solves the problem you were trying >to solve with the other approach, but enhances ease of use for >eveybody involved. Excellent. This is a change that won't take much effort and is relatively easy to test and ensure I don't add more bugs into the Auto FE Updater. I'm doing some family stuff for the next week so don't know if I'll get to this in that time. But this will be the focus of version 2.01. That and a toolbar on the top with icons but that might be version 2.02. Thanks again, Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/ |