Disassemble an MDE File

[Kareen bill]

Hi
I would like to ask you , about a way to disassemble the dot mde filles ,
can you help me in that

Thanks

Kareen.

PS. This was split from an article thread (How to Unsecure a Secure Access Database)

[ADezii]

Hii
I would like to ask you , about a way to disassemble the dot mde filles ,
can you help me in that

Thanks

Kareen.

a way to disassemble the dot mde filles

Kareen, I'm not really sure what you mean, please clarify.

[NeoPa]

Kareen, You need to ask the question, and it needs to be in its own thread. I've sorted the second bit out for you. You still need to add the question.

[missinglinq]

An .MDE file is essentially a black box, or to be more precise, a locked black box! You can use it to add and delete and manipulate information, within the boundries set up by the apps' developer, but you cannot access or alter the design of the database! Unless you have access to the .MDB file that it was made from, what you see is all you'll ever get! You cannot "disassemble" an .MDE file!

Welcome to TheSripts!

Linq ;0)>

[FishVal]

You may try this
http://www.everythingaccess.com/mdeunlocker.htm
It costs something but demo is free.

Or this http://accesstools.narod.ru/

[missinglinq]

"Quote: MDE Unlocker: Note: You cannot alter or gain access to the original VBA code - you must use Macros instead."

The reason I didn't mention these programs, and there are half a dozen on the market, is that, as it says, you can't access the VBA code! What it's doing, in essence, is guiding you thru re-creating your database by looking at the forms/reports and making a guess at what needs to be done to recreate the functionality. I've heard from a number of people over the years who've tried using them, and none of them were happy with the results. There are also (expensive) services that will do the same thing; take a look at the MDE and re-create the database. I guess it all depends on how complicated the app is and how badly you need to get inside to make changes. I personally can't imagine trying to develop a major database only using macros!

Linq ;0)>