When you write code using the RE7VBA tool that compiles the VBA code into a DLL to be deployed, the environment is very similar to the built in VBA environment. There is the same development environment and access to the same code. So you would think that switching between the two would not be a problem.

Read the rest of this entry »

At one time I was very keen on working with VBA on import. I now steer clear of this wherever possible! There are many reasons.

Read the rest of this entry »

If only we could change Raiser’s Edge in the same way that we can change other applications such as our favourite music players etc.

 Well unfortunately I cannot show you a way to do exactly that but there are a few things that can be changed. Read the rest of this entry »

If you are using VBA to perform actions on opening, saving or deleting record you have the option of putting the code in two different places.

Perhaps the most obvious is when you log in to RE as supervisor you can go into the Visual Basic for Applications environment (found under the Tools menu) and capture your events in the System project. This is the “inside” solution as it resides inside the database and can be programed from inside the RE application.

The other option is to use the RE7VBA tool. This executable is found in the Raiser’s Edge directory along side RE7.exe. Running this program opens up a similar environment except that you can save your work in a file and compile it to a DLL. This is the “outside” solution for opposite reasons

What are the pros and cons of each? Read the rest of this entry »