At 09:18 AM 9/20/2011, Paul Buckley wrote:
Good Morning List,
I just made an observation (actually I just found my screw up) and I thought
I'd share it with everyone using the 9.1 compiler. When you add additional
resources and define runtime licenses for add-ins (i.e. Power Plugins, RBZip,
etc.) you need to ALSO add the plugins themselves. I had some code that ran
fine in R:BASE and I got all kinds of errors in the compiled app. DUH!!!
After a good night's sleep and looking again, I realized I had entered my
licenses but not included the plugins (that's the .RBM files) themselves
(it's under a separate tab from the licenses).
So I'm once again I'm moving forward and a happy R:BASE camper once again.
At 09:22 AM 9/20/2011, Jan Johansen wrote:
I guess I should I have warned you first.
I did the same thing when I first used the new features in the compiler.
Glad you are back up and running.
Paul, Jan, and All R:BASE eXtreme 9.1 (32/64) Compiler Users:
FWIW, all R:BASE Plugin Modules (.RBM) MUST be placed in the same folder
with the compiled executable (.exe) folder. Placing the Plugin module in
the same folder with executable should have worked for you as well.
However, embedding Plugins, along with all additional resources, such as,
External Form Files, R:BASE Forms, R:BASE Reports, R:BASE Labels, Themes,
Runtime Licenses, and Miscellaneous Files is the best option to protect
and secure your application and investment in R:BASE eXtreme 9.1 (32/64).
Embedding R:BASE Engine into compiled executable is also a better option.
Very Best R:egards,
Razzak.
