Re: DLL Vs. EXE?
- From: "Peter T" <peter_t@discussions>
- Date: Fri, 13 Apr 2007 23:28:07 +0100
an advantage in the EXE approach: do not need to register
If it's an ActiveX EXE you still need to register, but with /RegServer not
regsvr32 as you would with a dll.
If you use late binding, in your VBA code if you can't create your entry
class, trap the error and call a separate routine to register the dll (in
code with Shell and you would need to know it's path or ask user to find it
if necessary).
Have you actually tried your Shell to EXE approach, in addition to which
you'd might want to look into "Shell & Wait". How do you go on to interact
between your VBA and the EXE, can be done but more difficult & limited.
Guess it depends on what you are doing overall.
Regards,
Peter T
"avi" <aviben@xxxxxxxxxxxxxxx> wrote in message
news:1176502176.758226.87930@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Helo Peter,
Thanks . I guess i'll opt for a dll as you suggested although i see(am
i wrong?) an advantage in the EXE approach: do not need to register
the DLL / I can put it as a part of the VBA code and call it with
Shell statement
Avi
.
- References:
- DLL Vs. EXE?
- From: avi
- Re: DLL Vs. EXE?
- From: Peter T
- Re: DLL Vs. EXE?
- From: avi
- DLL Vs. EXE?
- Prev by Date: Re: Making array in DLL available in VBA?
- Next by Date: Re: Counting Specific Number of Days across Multiple Months
- Previous by thread: Re: DLL Vs. EXE?
- Next by thread: Re: DLL Vs. EXE?
- Index(es):
Relevant Pages
|