May 25, 2017 at 7:16 pm
#4937
Moderator
As an aside…which perhaps I should have suggested at first 🙂
You can <make> a .BWS file have the same user experience as a .EXE – e.g. run as a shortcut, not have any visible BWS stuff, display forms etc. .BWS files have the benefit of being more flexible to different versions of BWS. Worst case, you may have to change the reference in VBA (if your development machine is a newer version of BWS than what is installed on the client's machine).