You can create a library db and add as a reference then you can access public constants. But that would require a non changing path. If these are common constants used in code i would distribute in a table like Pat said. What exactly are you doing?
I am also curious about why you would want to do this.
Even in an encrypted ACCDE or MDE, the definitions and values of public constants CAN be viewed. For example:
AFAIAC, this is a potential security issue that should have been fixed years ago.
For that reason, I'm not going to provide any assistance in ways of retrieving the values externally.
Having said that, I agree with the comments made by both @Pat Hartman and @MajP.
If these are your own databases and you need to get the values of public constants externally, make the MDE a library reference database or better still, put the values into a settings table. If the values are for 'sensitive' data such as passwords, make sure you encrypt them to prevent anyone viewing the values without authorisation.
If you are trying to hack into someone else's databases without authorisation, then I'll just say it can be done but I'm not going to provide details
Custom Database Property Did you know you can add a Custom Property to your MS Access Database file? You add it to the actual mdb or ACCDB, and yes it even works with mde or ACCDE! You can add things like a:- Copy Right Notice Author/Programmer Name dB Version Languages Serial Numbers Usage...