Dynamics Community Forum Thread Details

VBA and User Permissions

Hello:

I have successfully used VBA, to modify a window in GP 2013 R2 (12.00.1920).

Our users access GP through the Terminal Server and, specifically, through either a .rdp file created in Terminal Services admin tools or through VDI. Also, the end users only have "Read & Execute" permissions to the GP2013 code folder.

My VBA code is not based on a modified window. Rather, the window is unmodified.

Also, I have tested my programming on two test Terminal Servers. I have not placed this code on any of the production Terminal Servers.

All of that being said, do user permissions to the GP code need to be modified in order to access this window's "change" and, more importantly, to not receive any errors upon either logging into GP or opening the window?

Would the .rdp file need to be recreated and redeployed to the end users, in order to capture the change conducted by my VBA programming?

Would any "harm" be done, if I were to conduct this programming in production while users are logged in to GP? Likewise, if I find later that I need to modify or add to the programming, can I do so while users are logged in?

Thanks! Much appreciated!

John

Hi John -

It's always been my experience GP users need to have full control over the GP code folder; I also believe this is a best practice recommendation from Microsoft regarding Dynamics GP.

Access the modified window is granted through Alternate/Modified Forms and Reports. Even if you added VBA code to a window without modifying the window itself, Dynamics GP still considers this a modified window; this is indicated by the placement of periods on either side of the window title bar. A dot after the window title means the window has been included in a VBA project, a dot before the window title means the form has been modified (creating a FORMS.DIC) and I *believe* you'll still have to grant the users acces through Alternate/Modified Forms and Reports.

It's not recommended to make any code, window or report changes in production while users are in the system. When end users open Dynamics GP, they're also opening, loading and accessing any modified windows (FORMS.DIC) or reports (REPORTS.DIC) and *.vba files. There is a chance changing any of there objects while they're open and being accessed can lead to file corruption (I've seen it happen before). I would suggest making any changes to a test or development system, vetting the changes out, creating an package file and importing it into production when the users are out of the system.

Regards,
Sean

Quick Links

Leaderboard