IN THE SPOTLIGHT: MDE to MDB Conversion Service
(also supports: ACCDE to ACCDB, ADE to ADP, etc)
IN THE SPOTLIGHT: vbWatchdog
VBA error handling just got easier...
" vbWatchdog is off the chart. It solves a long standing problem of how to consolidate error handling into one global location and avoid repetitious code within applications. "
- Joe Anderson,
Microsoft Access MVP
Meet Shady, the vbWatchdog mascot watching over your VBA code →
(courtesy of Crystal Long, Microsoft Access MVP)
IN THE SPOTLIGHT: vbMAPI
An Outlook / MAPI code library for VBA, .NET and C# projects
Get emails out to your customers reliably, and without hassle, every single time.
Use vbMAPI alongside Microsoft Outlook to add professional emailing capabilities to your projects.
I don't believe this is possible. Can you prove it?
We understand that it's human nature to question something that is supposedly impossible to achieve - like converting a compiled MDE file back to full MDB format, including VBA source code.
To put the speculation to an end, a few years ago we took on the challenge to convert a compiled MDE back to a fully functioning MDB, in a public forum. The MDE was provided by Karl Donaubauer, Access MVP.
The results have since been written about in an article here (in German):
(Review by Karl Donaubauer, Access MVP)
Alex Dybenko (also Access MVP) was our common contact throughout the process, and he also writes about it in his blog here: Live test reverse engineering MDE to MDB
Many Microsoft Access developers claim that it is impossible to convert an MDE back into an MDB file, yet this is what you are claiming to achieve. Who am I to believe?
It depends! It is true that it is impossible to convert an MDE (or ADE) file back to its original form in its entirety. The service we offer recovers all Access objects with one exception: source-code comments.
When an MDE file is created, all source code (including comments) are removed from the file. The file still works however since the VBA compiled code remains in the MDE file. The compiled code is a binary interpretation of the VBA source code - it is not easily human-readable.
Fortunately our experienced developers are capable of interpreting the compiled code in an MDE file and recreating a new fully compatible version of the original source code.
Using advanced techniques, our developers can also recover all procedure and variable names. Using this extra information we can recreate your code almost exactly to the original standard. The few differences between the original VBA code and the new VBA code can be seen in this example (but note there are no functional differences):
How long does it take for you to convert an MDE into an MDB file?
Converting an MDE into an MDB file is a complex process. Once you've provided us with information about your project (such as project file size) we will be able to give you a free quote.
In general, most projects can be reverse engineered within 48 hours.
How much do you charge for this service?
The cost is largely dependant on the complexity of the compiled VBA project in your project. We provide a free no-obligation quote on request.
Our costs reflect the time and effort involved in converting your project in a professional manner. To our knowledge, no other service is available that is capable of producing similar results and accuracy.
I have an ADE file - can you reverse engineer that too?
Yes, our experts are capable of converting MDE, ACCDE or ADE files back to their original formats from Access 97 right through to the latest version of Access (v2016 as of writing).
I have an Access 97 MDE file which I would like upgraded to Access 2003, is this something you can do for me?
Certainly. Once your project has been converted back to its source format, any experienced Access developer should be able to assist you in upgrading your project to another Access version. If you would like our experienced engineers to do this for you, please talk to us after the conversion work has been completed.
I've heard that reverse engineering source code often produces "spaghetti code", where the result is a working version, but not easily maintainable since the code is essentially a representation of how the computer interprets the code not how the original developer wrote it. Is this true?
This is true of most 'decompiler' type software. However, our reverse engineering experts are also experienced developers and the quality of the resulting VBA code is an example of this. As an example, most decompilers don't recognise loops and condition statements at all, yet we do. You can be rest assured that your 'recovered' VBA code will be of the same quality or higher quality than the original VBA code.
It sounds too good to be true. How come you can do what others can't?
Our engineers are very competent developers and understand all Access database formats at the binary level. The knowledge that was gained from running our Access database repair service provided the groundwork for this service.