2003

Had thoughts of compiling some Excel VBA into a ..dll file.

I thought that I needed just AppSentinel. But it appears that I need VB or something like
Visual Studio.

Could someone send some links and/or share a few sentences?

TIA EagleOne

AppSentinel is nothing to do with creating a dll file, it is a licensing
product, one that can stop your product running if the registration code has
not been supplied.

If you want to create a dll, say to make some code run faster or to hide,
then a dll is one way, but for that you do need full VB.

--
HTH

Bob Phillips

(replace somewhere in email address with gmail if mailing direct)

wrote in message
...
2003

Had thoughts of compiling some Excel VBA into a ..dll file.

I thought that I needed just AppSentinel. But it appears that I need VB
or something like
Visual Studio.

Could someone send some links and/or share a few sentences?

TIA EagleOne

Hello Bob,

What s/w can I use to "compile" XL VBA into a DLL?

Thanks

"Bob Phillips" wrote:

AppSentinel is nothing to do with creating a dll file, it is a licensing
product, one that can stop your product running if the registration code has
not been supplied.

If you want to create a dll, say to make some code run faster or to hide,
then a dll is one way, but for that you do need full VB.

Actually, my goal is to protect some VBA code. My thoughts are to have an XL user be able to "Run"
a macro in XL yet have more protection than a VBA password as I have heard is easily hacked.

I am very interested in your comment "then a dll is one way."
What other ways might there be?

EagleOne

"Bob Phillips" wrote:

AppSentinel is nothing to do with creating a dll file, it is a licensing
product, one that can stop your product running if the registration code has
not been supplied.

If you want to create a dll, say to make some code run faster or to hide,
then a dll is one way, but for that you do need full VB.

There are other ways, such as creating an XLL add-in, but that is using C++
so may be further than you want to go and you need the developers kit.

Another option is to be a VB application that accesses an excel workbook via
automation. But this requires a different perspective, you need to be a lot
more careful how you reference objects etc. (nothing that you shouldn't do
anyway, but it often defaults in Excel and so is easy to overlook), and
knowing how to access the object model via automation.

But a DLL is the best and easiest way to do it IMO. You should be able to
get a copy of VB on eBay for a reasonable sum.

--
HTH

Bob Phillips

(replace somewhere in email address with gmail if mailing direct)

wrote in message
...
Actually, my goal is to protect some VBA code. My thoughts are to have an
XL user be able to "Run"
a macro in XL yet have more protection than a VBA password as I have heard
is easily hacked.

I am very interested in your comment "then a dll is one way."
What other ways might there be?

EagleOne

"Bob Phillips" wrote:

AppSentinel is nothing to do with creating a dll file, it is a licensing
product, one that can stop your product running if the registration code
has
not been supplied.

If you want to create a dll, say to make some code run faster or to hide,
then a dll is one way, but for that you do need full VB.

Thanks Bob


Bob Phillips wrote:
There are other ways, such as creating an XLL add-in, but that is using C++
so may be further than you want to go and you need the developers kit.

Another option is to be a VB application that accesses an excel workbook via
automation. But this requires a different perspective, you need to be a lot
more careful how you reference objects etc. (nothing that you shouldn't do
anyway, but it often defaults in Excel and so is easy to overlook), and
knowing how to access the object model via automation.

But a DLL is the best and easiest way to do it IMO. You should be able to
get a copy of VB on eBay for a reasonable sum.

--
HTH

Bob Phillips

(replace somewhere in email address with gmail if mailing direct)

wrote in message
...
Actually, my goal is to protect some VBA code. My thoughts are to have an
XL user be able to "Run"
a macro in XL yet have more protection than a VBA password as I have heard
is easily hacked.

I am very interested in your comment "then a dll is one way."
What other ways might there be?

EagleOne

"Bob Phillips" wrote:

AppSentinel is nothing to do with creating a dll file, it is a licensing
product, one that can stop your product running if the registration code
has
not been supplied.

If you want to create a dll, say to make some code run faster or to hide,
then a dll is one way, but for that you do need full VB.