Accessing code in an .MDE file?

[lambic]

Hi,

Probably a stupid question, but is there any way to access the code behind forms e.t.c. in an .mde file?
We don't have an original copy of the .mdb to work off.

Thanks

 

[sshowers]

Not a stupid question, but an unfortunate answer. Here is the information found in the Access 2000 Documentation:

About MDE files:
If your database contains Microsoft Visual Basic code, saving your Microsoft Access database as an MDE compiles all modules, removes all editable source code, and compacts the destination database. Your Visual Basic code will continue to run, but it cannot be viewed or edited, and the size of your Access database will be reduced due to the removal of the code. Additionally, memory usage is optimized, which will improve performance.

Saving your Access database as an MDE file prevents the following actions:

1) Viewing, modifying, or creating forms, reports, or
modules in Design view.

2) Adding, deleting, or changing references to object
libraries or databases.

3) Changing code using the properties or methods of the
Microsoft Access or VBA Object models — an MDE file
contains no source code.

4) Importing or exporting forms, reports, or modules.
However, tables, queries, data access pages, and
macros can be imported from or exported to non-MDE
databases. Any tables, queries, data access pages,
or macros in an MDE file can be imported into another
Access database, but no forms, reports, or modules
can be imported into another Access database.

Caution Be sure to save a copy of your original Access database. If you need to modify the design of forms, reports, or modules in an Access database saved as an MDE file, you must open the original Access database, modify it, and then save it as an MDE file again. Saving an Access database containing tables as an MDE file creates complications reconciling different versions of the data if you need to modify the design of the forms, reports, or modules later. For this reason, saving a Access database as an MDE file is most appropriate for the front-end database of a front-end/back-end application.

Caution You won't be able to open, convert, or run code in a Microsoft Access 2000 MDE file in future versions of Microsoft Access. The only way to convert a Microsoft Access 2000 MDE file to a future version will be to open the original Access database the MDE file was created from, convert it, and then save the converted Access database as an MDE file.

----------
Personally, I have not found a way around this -- but maybe there are some hackers out there with a different answer...

--sshowers

 

[KornGeek]

I would be interested to find out if anyone has found a way to hack into the code. I'm always interested to know just how secure the security features really are. Sleep is for people with no caffeine.

 

[Pisi]

Does somebody know how to hide(not in Tools/Options and Hidden attribute) the queries in a MDE database. I don't want users to see the definitions of the queries.

Thank you

 

[KornGeek]

I believe you can hide queries as system objects by naming them with USys as the first 4 characters. However, users can view these as easily as viewing Hidden objects. If you abosultely need to keep them secret, use VB code instead of queries. In an MDE (to my knowledge) there is no way for the users to view the code. Sleep is for people with no caffeine.

 

[gusbrunston]

[tt]
Hi, Iambic:

When you make an .mde file, the wizard checks to make sure there is a back up .mdb file. Before you jump, why not search your drive with the name of your mdb file and maybe it got lost somewhere.

Other possibilities: a copy on a user's workstation; zip drive; old floppies; cdr's...then again, you've probably done this already...

Check out Jimmy the Geek's (2) automated back up routines in the FAQ's on Tek-Tips. [tt] Gus Brunston - Access2000(DAO)[/tt] Intermediate skills.