Videos for Admins

Videos for Administrators

Modernize your Mainframe Application with Reflection Desktop and Enterprise Server (3:17)

Deploying Specific Settings(3:55)

Sharing Macros in the Common Project (2:24)

Sharing Macros in Session Documents (3:39)

Broadcasting Commands to Multiple Sessions

Setting up for Deployment

Setting up a Basic Deployment

Simplifying Deployment with Compound Session Documents

Setting up Information Privacy

Setting up Reflection Desktop with a User Interface like Extra!

Customizing the Ribbon

Creating Transforms

Packaging Configuration Files

You can import macros into the VBA common project without affecting other code modules in this project. You can use this approach to update these macros without overwriting custom macros that users may have saved in this project.

Audio Transcript:

0:04 - 0:10
This video shows how to import macros into the VBA common project without affecting other code modules in this project.

0:11 - 0:37
Macros in the Common Project can be called by any session macro and are saved in the vbaProject.bin file.
You can share these macros by deploying this file and then redeploying it  when you need to update your macros.
But if you use this approach, you’ll have to redeploy the file every time you update your macros and users will lose any macros they have saved in the Common Project.

0:38 - 1:07
We’ll show how to set up Reflection to import macros into this project from a file on a share.
First we’ll create the macros you want to share in a module in the Common Project, export that module into a .bas file, and then place that file on a share.
Then we’ll create a macro in the Common Project that references that file. This macro is automatically saved to the vbaProject.bin file in the Appdata folder.

1:08 - 0:14
In VBA, we’ll insert a module in the Common project and give it a descriptive name.
                
1:18 - 0:24             
Enter the code we want to share.
Then export the module to a  bas file and save that file on a share.
                                
1:27 - 1:32             
Now we’ll create a macro that imports the module into the Common Project when Reflection opens. 

1:34 - 1:39     
This code removes the module if it’s already in the Common Project and imports the module into the project.
                
1:39 - 1:44             
Next we’ll set Reflection to run this macro every time it opens.
                
1:44 - 1:48                     
In Workspace settings, we choose Configure Workspace Defaults.

1:52 - 2:16     
And then set a startup action that runs the macro.
These settings are saved in the application.settings and frame.settings files in the Appdata folder.
You’ll need to deploy these files and the vbaProject.bin file created earlier to that folder.
And that’s how you can import your macros into the VBA Common Project without affecting any user macros in that project.