Re: Design Guidelines for Non-Power Users?
From: MikeD (nobody_at_nowhere.edu)
Date: 10/20/04
- Next message: Randy Birch: "Re: MSComctlLib missing...where do I look?"
- Previous message: Randy Birch: "Re: Language of MessageBox in VB6"
- In reply to: George: "Design Guidelines for Non-Power Users?"
- Next in thread: George: "Re: Design Guidelines for Non-Power Users?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 19 Oct 2004 20:23:10 -0400
"George" <nospam@please.com> wrote in message
news:OcoIRAgtEHA.2876@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> I am building a VB6 application that will need to run with limited (user)
> privileges. I understand that non-power users only have write access to a
> few specific directories on the system, as well as very limited registry
> access.
>
> However, I cannot find a definitive guide as to exactly what resources are
> available to limited users. Do you know of any such listing? What are the
> guidelines to building VB6 applications that will be run in limited mode?
>
The following is primarily intended as general information.
Non-Power Users and Admins will not be able to install your app. The app
must be installed under a login that has PowerUser or Admin rights. However,
if the app is installed for All Users, then the "regular" users (referred to
as just Users from here on) should be able to run it.
Users may very well be restricted from reading, and particularly writing to,
various folders on their own hard drives. Any information your app needs to
write to disk should probably be written to an appropriate folder in the
User's profile directory (for example, H:\Documents and Settings\User
Name\Application Data). You can get whatever this folder happens to be by
calling the SHGetSpecialFolderLocation API function. For code examples of
calling that function, search www.google.com. Obviously, there are a number
of other folders the User shouldn't have any problem reading/writing, such
as their own My Documents folder. It's quite possible the User WON'T have
write permissions for even the application's folder (the folder the app is
installed to), though. If they don't have write permissions, this could
cause problems For example, if your app opens an Access database located in
that folder, you might not be able to open a connection to it because Jet
can't create the lock file.
The only part of the Registry a User has write permissions for is
HKEY_CURRENT_USER (and most subkeys). However, a User should have read
permissions for most other parts of the Registry (for example,
HKEY_LOCAL_MACHINE).
Here's the best advice I can think of to give you: TEST your app very
thoroughly on a PC (and other than your dev PC) under a login that will have
the exact same permissions as the users who will be using your app (IOW, a
login that belongs only to the Users group plus whatever other special
permissions, if any, they might be granted). You may need to consult with
the SysAdmin on this.
Mike
- Next message: Randy Birch: "Re: MSComctlLib missing...where do I look?"
- Previous message: Randy Birch: "Re: Language of MessageBox in VB6"
- In reply to: George: "Design Guidelines for Non-Power Users?"
- Next in thread: George: "Re: Design Guidelines for Non-Power Users?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|