[AccessD] Hacking MDE (was Creating a demo Access app?)

>  It's not even really undocumented.  No where does it say you can't use 
> OLE
> against a MDE (or course it doesn't say that either, so I suppose you 
> might
> call it undocumented).
Jim,

Unfortunately there is much easier way than OLE against running MDE...

<<<
> just that no one had bothered
> to do it because of the size of the task vs. the worth
>>>
Somebody bothered to write VB6 decompiler mentioned here a while ago.
Was writing this decompiler worth the trouble?
There is no answer because they hide their coordinates.
But they are making it better.
And my guess it was used to copycat interfaces of the software, which I 
talked here about.
VBA p-code can be easily extracted from mde.
The unknowns who are developing VB6 decompiler know that for sure I think.
They can succeed with VBA decompiler as they did with VB6 one.

Shamil

----- Original Message ----- 
From: "Jim Dettman" <jimdettman at earthlink.net>
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Sent: Monday, February 27, 2006 5:02 PM
Subject: Re: [AccessD] Hacking MDE (was Creating a demo Access app?)


>
> <<In fact it's very easy and it can't be even called as hacking because it
> uses undocumented feature and not more than that.>>
>
>  It's not even really undocumented.  No where does it say you can't use 
> OLE
> against a MDE (or course it doesn't say that either, so I suppose you 
> might
> call it undocumented).  Mike Gunderloy pointed this out many years ago. He
> was also the first (that I'm aware of) to point out that is was 
> technically
> possible to de-tokenize VBA p-code from a MDE, just that no one had 
> bothered
> to do it because of the size of the task vs. the worth.
>
>  If it was simple as the one language I use (NPL), which has built in
> statements to do that ($Source and $Object) on the fly, we'd really be in
> trouble.
>
> Jim.
>

<<< tail skipped >>>