Fishing for Ideas: Keeping Casual users out of the back end

[Clif McIrvin]

Background: We have a small office with generally "non-savvy" users.

I have a somewhat dis-organized jumble of front and back ends in a
server share, and would like to establish a system for locating the
various files.

I'm thinking of leaving the back ends where they are, and moving all the
deployment master copies of the front ends into folders under that same
share (I'm now using Tony's Auto FE Updater*). Now, if one of the users
navigates to the share to open the app (instead of using their local FE
shortcut) they will find only BE mdbs and shortcuts for the various FEs
created by Tony's Auto FE Updater.

Next, I'm planning to add a start-up form to each BE that says "This is
not the wonderful process application you are looking for. Close this
window and use the wonderful process shortcut, which will place a
shortcut on your desktop for your future use." The only option on this
form will be an OK button, which will exit the database.

What do you think? Any comments or suggestions for me?

[*]Auto FE Updater Copyright Tony Toews
www.autofeupdater.com

 

[chippy]

Dear Clif,
For a nominal fee I can build this for you. If you would like email me and
we can discuss further.

 

[Douglas J. Steele]

Please note that these forums are intended for free peer-to-peer help.

Advertising is not permitted, nor is soliciting for work acceptable.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Dear Clif,
For a nominal fee I can build this for you. If you would like email me
and
we can discuss further.

Background: We have a small office with generally "non-savvy" users.

I have a somewhat dis-organized jumble of front and back ends in a
server share, and would like to establish a system for locating the
various files.

I'm thinking of leaving the back ends where they are, and moving all the
deployment master copies of the front ends into folders under that same
share (I'm now using Tony's Auto FE Updater*). Now, if one of the users
navigates to the share to open the app (instead of using their local FE
shortcut) they will find only BE mdbs and shortcuts for the various FEs
created by Tony's Auto FE Updater.

Next, I'm planning to add a start-up form to each BE that says "This is
not the wonderful process application you are looking for. Close this
window and use the wonderful process shortcut, which will place a
shortcut on your desktop for your future use." The only option on this
form will be an OK button, which will exit the database.

What do you think? Any comments or suggestions for me?

[*]Auto FE Updater Copyright Tony Toews
www.autofeupdater.com


--
Clif


.

 

[Clif McIrvin]

Gee ... is this Steve?

go Away.

 

[Tony Toews [MVP]]

Next, I'm planning to add a start-up form to each BE that says "This is
not the wonderful process application you are looking for. Close this
window and use the wonderful process shortcut, which will place a
shortcut on your desktop for your future use." The only option on this
form will be an OK button, which will exit the database.

What do you think? Any comments or suggestions for me?

Yes, I have such a form in my BEs as well.

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/

 

[Tony Toews [MVP]]

For a nominal fee I can build this for you. If you would like email me and
we can discuss further.

If you're going to post a blatant solicitation for work the least you
can do is use an email address that works.

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/

 

[Tony Toews [MVP]]

Yes, I have such a form in my BEs as well.

Given the A2007 Trusted Locations stuff put a macro behind that close
button and not VBA code. Otherwise, if you are running A2007, the
user will be able to click on the close button but nothing will
happen.

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/

 

[Clif McIrvin]

Given the A2007 Trusted Locations stuff put a macro behind that close
button and not VBA code. Otherwise, if you are running A2007, the
user will be able to click on the close button but nothing will
happen.

Thanks! While this office is using A2003, we do have another office
using Office 2007 and I'd never have thought of that.

 

[Larry Linson]

Dear Clif,
For a nominal fee I can build this for you. If you
would like email me and we can discuss further.

There are many here who could help, and would help here, for free. They
understand that this newsgroup is for free peer-to-peer assistance, so do
not solicit you for fee business. Even if you could reach "chippy", the fact
that he/she/it does not realize that the phony e-mail generated when you
post via the online interface would not be a high recommendation of
his/her/its general knowledge. Oh, well...

Larry Linson
Microsoft Office Access MVP

 

[(PeteCresswell)]

Per Clif McIrvin:

Next, I'm planning to add a start-up form to each BE that says "This is
not the wonderful process application you are looking for. Close this
window and use the wonderful process shortcut, which will place a
shortcut on your desktop for your future use." The only option on this
form will be an OK button, which will exit the database.

What do you think? Any comments or suggestions for me?

Works for me as long as the users are not hostile or you don't
need to explicitly prevent them from looking.

Otherwise, it sounds like SQL Server and views/stored procedures.

 

[Clif McIrvin]

Per Clif McIrvin:

Works for me as long as the users are not hostile or you don't
need to explicitly prevent them from looking.

Otherwise, it sounds like SQL Server and views/stored procedures.

Thanks Pete. I understand your caveats ... and for now am making the
choice to pretend they won't become an issue. <grin>