M
makyland
After having tried (with no success though) to follow Microsoft instructions
to get the 2003 runtime version of Access (I have Visual Studio Tools for
Office and many other things, but never get to find how to do it...) I'm
considering the option of the 2007 run-time, but obviously the first question
you wonder when you've never opened Access 2007 would be:
"I do need to have installed Access 2007 to deploy a solution with the
Access 2007-run-time version, don't I?"
Or
"Is it possible to deploy an Access 2002-2003 file with Access 2007
run-time? is it backward compatible?" (I mean, no need to convert the file
opening it with an Access 2007 version and then make the deployment package)
I have already downloaded the Access 2007 developer extensions, but haven't
opened it yet because I consider it is really important that I know what I'm
doing before messing things up.
Also, giving a different point of view to this same question, my real
worryness is not that my users have or not have Access installed but the fact
that they have many different Access/Windows installations and are suffering
many problems with corrupted or missing DLLs and failing Microsoft Data
Access Components, so I'm struggling myself to find an homogenous solution
that we can guarantee that will install all the necessary components for the
application to work as a stand-alone application. So my third question will
be: "Deploying my application with a run-time Access version will include a
"working" version of the main dlls required to guarantee the application will
work properly after the installation?"
I will appreciate so much any support on this.
Thanks in advance!
to get the 2003 runtime version of Access (I have Visual Studio Tools for
Office and many other things, but never get to find how to do it...) I'm
considering the option of the 2007 run-time, but obviously the first question
you wonder when you've never opened Access 2007 would be:
"I do need to have installed Access 2007 to deploy a solution with the
Access 2007-run-time version, don't I?"
Or
"Is it possible to deploy an Access 2002-2003 file with Access 2007
run-time? is it backward compatible?" (I mean, no need to convert the file
opening it with an Access 2007 version and then make the deployment package)
I have already downloaded the Access 2007 developer extensions, but haven't
opened it yet because I consider it is really important that I know what I'm
doing before messing things up.
Also, giving a different point of view to this same question, my real
worryness is not that my users have or not have Access installed but the fact
that they have many different Access/Windows installations and are suffering
many problems with corrupted or missing DLLs and failing Microsoft Data
Access Components, so I'm struggling myself to find an homogenous solution
that we can guarantee that will install all the necessary components for the
application to work as a stand-alone application. So my third question will
be: "Deploying my application with a run-time Access version will include a
"working" version of the main dlls required to guarantee the application will
work properly after the installation?"
I will appreciate so much any support on this.
Thanks in advance!