Packaging Access 2002
It's me again! :) I'm also packaging Access 2002 and had a quick question. The users in my environment currently have Access 97 installed (we support way too many different versions of Access at my place). Now when deploying Access 2002, it changes the file association so all Access databases open with Access 02 instead of Access 97. Can anyone tell me how I can change the file association (registry hack?) so that Access 97 stays the default.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
jonasm
17 years ago
Posted by:
dpolishsensation
17 years ago
Thanks for the reply jonasm. I was thinking that's the way I would have to do it. I'm packaging with Wise Package Studio. I'm not sure how I'm going to do this yet but I was thinking of importing a key from another machine that I created that forces or locks down Access 97 as the only program to open Access databases. In order for someone to open a database in another program, they would be forced to right click and select "Open With." Right now I'm trying to figure out how to do this. Anyone have any ideas how I would write a key to do this or even if what I'm explaining would work?
Posted by:
nheim
17 years ago
Posted by:
dpolishsensation
17 years ago
Thanks nheim, that works great!!! I have another issue though. We have other versions of Access on our machines that we use. This locks it down too much as users will be unable to do "Open With" and change to a different version of Access if need be. So I want Access 97 to be the default database program but I would still like to have the option to change to other database programs with "Open With." Please advise.
Posted by:
nheim
17 years ago
Hi Marek,
play around with these tables. First, i would just rename the 'Extension' entry (e.g. mdb) in the Extension table to something new. That should install all the handlers, but not to the normal extension.
The 'Open with...' should work all the time, because, there is the possibility to choose a new program with full path. So, maybe, this isn't necessary at all.
Regards, Nick
play around with these tables. First, i would just rename the 'Extension' entry (e.g. mdb) in the Extension table to something new. That should install all the handlers, but not to the normal extension.
The 'Open with...' should work all the time, because, there is the possibility to choose a new program with full path. So, maybe, this isn't necessary at all.
Regards, Nick
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.