Disclaimer: I’ve never done anything similar, but I’ve been thinking about it as an option in recent months.
I think it depends on how the mde references the backend. Most likely, you’re going to have to rewrite code or the reference to the backend and then re-comple to convert into a new mde.
What I have been thinking of doing for myself is this:
Include the backend location as a field value within a table that’s used to store all the default values. When the mde is opened, it would first look to see if the mdb backend is present. If not, it would go look to see if a specific file is present in a specific location. If yes, it can open this text file and read the ‘instructions’ from the file. Instruction would be to change the field value in the Defaults table (for the backend mdb location)
What I’m not certain of (mostly because I haven’t tried to actually do this yet) is whether you could use the built in re-link option after changing a few values or if you’d have to remove all table links and then rebuild them. My first guess is the latter.
- Now Tracking down where the backend reference might be. It may not be anywhere specific. If the tables are linked, you might find the information in the TableDefs object.
Mike
