why don't you just create the com object in VB6? Isn't that what Dave P is
hinting at?

wrote in message
...
Peter,

I have not yet ported my VBA to .net. Last week, I spent a good deal of
time learning how to create
a DLL in VB.NET. Purpose to secure my VBA code. Then I found out that I
could not just copy my VBA
code into a VB.NET Class section then compile. That can not be done.

So I'm thinking of Plan B which is leaving it in VBA but making it
difficult to reach.

What I do want to do is to migrate the Ontime code to a VB.NET DLL. I
realize that I may have to
use VB.NET equivalent if available. Then I'll load/execute the DLL which,
hopefully, will work in
VBE.

Thanks for you help - which was significant.

EagleOne


"Peter T" <peter_t@discussions wrote:

I don't know much about .NET but pretty sure it doesn't have an OnTime
method like VBA, though there will be alternatives of course.

I'm missing something, why would you be concerned about someone breaking
your VBA password if no longer have any VBA code and have ported
everything
to .NET.

As for decompiling - I've read that .Net-visualbasic can be hacked but
you'd
need to be very familiar with .NET to be able to do that and then for it
to
be worthwhile. Curiosity - why do you think someone might go to the
lengths
of doing that. (FWIW a VB6 dll is virtually impossible to decompile.)

Regards,
Peter T



wrote in message
. ..
Another XL brainiac is heard.

Dave, I just finished a week of COM addin study based on Chip's
excellent
information.

Based upon my reading, I must migrate my VBA to VB.NET to get my
procedures and functions to compile
(.dll) in VB.NET.

So as Plan B, I am planning a COM Addin with a Ontime routine to check
if
someone has successfully
defeated the VB password. Maybe I am just fooling myself. My guess is
that hackers can reverse
engineer dll's.

Are you aware of any short/sweet written recap(s) and/or s/e migration
packages which will migrate
VBA to VB.NET?

Thanks for your time and knowledge.

EagleOne

Dave Peterson wrote:

Ps. That site is Chip Pearson's.

Dave Peterson wrote:

If you don't trust protecting the project, then I hope you wouldn't
trust
anything written in VBA--since macros can be disabled.

Maybe it's time to learn about compiled languages and COM addins.

I'd start he
http://www.cpearson.com/excel/CreatingCOMAddIn.aspx

wrote:

Jim is heard from!

Jim you and I know that cracking passwords is simple and done all
the
time. I need something more
clever.

Thanks

"Jim Cone" wrote:


If you password protect the project in the VBE then users can't
open
the project.

--

Dave Peterson