Gustav Brock
Gustav at cactus.dk
Thu Apr 28 07:10:20 CDT 2005
Hi Virginia Like Brett I will warn you too to proceed with this. Changing the display settings for pure cosmetic reasons is very serious, it may not be possible at all (due to lack of user rights), some users will be ready to kill you for delivering such an amateur "I own it all and to He.. with your settings"-app, and you will not be able to reset the settings if the user has made changes not saved in a theme. Now don't say you haven't been warned ... /gustav >>> HollisVJ at pgdp.usec.com 04/28 1:45 pm >>> That makes sense. I will make sure I turn it back on when they close the dB. Most users probably wouldn't notice at all, few other databases around (in Access anyway). But setting it back is a good idea. Thanks. Virginia *************** If I may respond... I agree with Brett, if your apps are working in an environment where your users are going to be aware of what's happening and be concerned about it. If not - the options are all yours! Dan Waters -----Original Message----- From: accessd-bounces at databaseadvisors.com <http://databaseadvisors.com/mailman/listinfo/accessd> [mailto:accessd-bounces at databaseadvisors.com <http://databaseadvisors.com/mailman/listinfo/accessd> ] On Behalf Of Brett Barabash Sent: Wednesday, April 27, 2005 3:55 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] A2003 Tab Control If I may be so bold... Automatically changing another user's global settings to suit your application's needs is considered by many (like myself) to be very intrusive, and generally a poor practice. However, there are valid reasons for needing to do this (I think you may have touched upon one). In this case, I would strongly suggest keeping track of the user's original settings when your app launches and restoring them when it closes. Otherwise, be prepared for the confused users asking you why their other Access apps look "different" since they ran yours.