E
Ed Warren
I have an application built to run with Access Runtime 2003.
(MyApplication.mde)
Some Client machines do not have Access installed --> no problem install
runtime and we're done
Some Client Machines have Access 2003 installed (I don't want to touch their
acess install), just let them run the application
Some Client Machines have earlier Access versions( I want to install the
2003 runtime, but not mess up their current Access Installs). When I tried
this on one of my development machines, the Runtime "took over" the *.mdb
extension and when I tried to open any access file it fired up on the
runtime version. I need to make sure this does not happen and since I have
no access to the client machines other than the application install routine
I need to know the 'best' , 'a safe way' to set up my application and not
mess with their other versions of Access.
Thanks,
Ed Warren.
(MyApplication.mde)
Some Client machines do not have Access installed --> no problem install
runtime and we're done
Some Client Machines have Access 2003 installed (I don't want to touch their
acess install), just let them run the application
Some Client Machines have earlier Access versions( I want to install the
2003 runtime, but not mess up their current Access Installs). When I tried
this on one of my development machines, the Runtime "took over" the *.mdb
extension and when I tried to open any access file it fired up on the
runtime version. I need to make sure this does not happen and since I have
no access to the client machines other than the application install routine
I need to know the 'best' , 'a safe way' to set up my application and not
mess with their other versions of Access.
Thanks,
Ed Warren.