I could be wrong, but here's my guess. Every reference to the definition of MDE I can find explains that it's a "Microsoft Access MDE Database". In this case MDE could mean Multiple Data Entry, so MDE would in a way be a recursive acronym which ultimately sorts out to "Microsoft Access Multiple Data Entry Database".
MDE - Microsoft Data(B)ase - Encoded/Encrypted? As in, "I compiled the MDB so now the code modules and forms/reports are compiled, thus they are "encoded"? I don't mean encryption in the PGP sense, more the "unable to read, thus it's encrypted" sense.
The original (Access 1) filename extension was ".mdb", for "Microsoft Database". All database file extensions since that time have started with ".md", so that's where that part comes from. Whether it "means" anything is a matter of interpretation.
I have always pretty much assumed the "e" was short for "executable". It contains code compiled to machine language, the way VB does. (Actually, I think it's threaded code, which is a hybrid of machine language and interpreted language.) It's not actually executable all by itself, because that would make it tougher to access the built-in data (Jet would have to be able to understand the EXE header, for instance, and you wouldn't be able to associate the extension with msaccess.exe for opening the database). But if you include the .mde and the runtime library in an install package (using the PD wizard), it becomes a standalone program analogous to a product offered for sale--an executable, in other words.
Rick Sprague
Want the best answers? See faq181-2886 To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.