problem with startup properties

[sunil sharma]

Hi all,

I want urgent feedback on my request. I have to clear the AllowSpecialkey from the startup properties based on the workgroup user security so that the user may not see the database window and VBE. My Application is multiuser Application and it runs thru Terminal Server services. Application sets the AllowSpecialkey properly but it is not working for the first time. For example, say application will clear the AllowSpecialKey for users from security group X and will set the AllowSpecialKey for users from Security group Y. Now when the user from X logs in, Applications sets the AllowSpecialKey to false via script called from AutoExec Macro. But the changes are not reflected immediately. When user from X logs in for the second time , then the Application behaves in desisred manner .

Can anybody help me in this. I want the Application to have the changes took place at the time user logs in.

[zzqxxq]

At the point that you run the AutoExec macro, the MS Access environment is already created so that its too late to change to the global environment (such as setting or resetting AllowSpecialKey) . The MS Access help file on AllowSpecialKey states specifically that this does not take effect until the next time the database is opened so you will not get the result you want via this method.

Access does provide command line startup functions however that may fit the bill - in Access help type in "command" and one of the subjects will be command line parameters - check them out especially /wrkgrp - you may be able to create a workgroup profile for each workgroup that will do what you want on startup based - there are other options also such as /user etc. I think this will help you