You can use your favorite social network to register or link an existing account:
Or use your email address to register without a social network:
Sign in with these social networks:
Or enter your username and password
Forgot your password?
Yes, please link my existing account with for quick, secure access.
No, I would like to create a new account with my profile information.
Tips
How-to
News
Videos
Stories
Today’s guest writer is Neha Monga, the Access PM responsible for the runtime. she was recently asked a few questions that are likely worth sharing more broadly.
Question: Is it in the design of Access 2007 runtime to be able to run in the SAME PC as one where there is already another Access License installed?
[Neha] Yes. Access 2007 runtime should be able to run with concurrent installations of other versions of full blown Access.
Question: Can the RunTime2007 application xxxx.accdr run on the same system as an yyy.mdb file whether it is Access2003 or Access2002 or Access 2000 or Access97 license already installed and there could be some older access applications running there perhaps?
[Neha] You are right. In that case your .accdr files will open with Access 2007 runtime. Do keep in mind is that if you have multiple versions of Access installed, then your other .mdb files will open with the “last run” version of Access or Access runtime. So when you try to open an .mdb file, it will open with Access 2007 runtime if that was the run last. The workaround to have your .mdb filed open in Access full-blown versions, is to launch open Access (XP, 2003, whatever you may have) and let it register as “last run” version of access. Next time, your .mdb files will open with that version of Access instead.
Question: I assume if a customer had Access2007 installed by any chance then the xxx.accdr would run under the full Access2007 without the need to download the AccessRunTime.exe file?
[Neha] Correct!
Question: What I am getting at is to try and deliver just one database in RunTime2007 mode so that I do not have to deliver an alternative yyy.mde file to run on older access licenses. Can I do that?
[Neha] You should always read the licensing agreement first—we don’t give legal advice through the blog.
You should be able to do deliver one database with Access runtime 2007 and it should work regardless of other Access full licenses installed on the users’ PC.
Furthermore, you can also make use of the packaging solution in ADE (Access Developer Extension) and create your custom msi with all the files and runtime bundled together. It also allows you to create a custom icon to launch your app with the runtime on the PC. You can find more information here.
Comments: (74) Collapse
I've been following the issue of concurrently running multiple Access versions for a while now. I can't say I've actually found any solution except purchasing 3rd party installers. Erwin Leyes have been going on about Thinstall (Erwin, Thinstall is too E-X-P-E-N-S-I-V-E for most of us!). I've seen people talking about Sagekey's MSI Wizard. Would this not have been the solution to Dan Gleason's problem? Albert, can you tell me about "VPC" you're referring to?
erwin leyes: "Maybe..maybe... maybe.....SAGEKEY has spies inside MS ACCESS TEAM." It seems you are right... unfortunatelly... :-(
MammAfrica; Other smart solution is VMWARE only or MS Virtual PC, Run your application in a virtualized environment. Just add some instruction to your User/client. I also tried this solution and again you can save but its not really smart like compiled thinstall apps wherein you just copy and paste your finish EXE and can run even in usb or Linux OS using Wine Emulation. "If you really want the smart solution then there are so many solutions or ideas. But If you dont want, then there are also many reasons". VIVA Postgre or MySQL as Ms Access Backend!!
I totally agree with the post that Erwin pointing out thininstall might come down in the future does absolute NOTHING for us here. Flying cars might become affordable in the future too, but now it just useless information. Suggesting some technologies like thininstall is great for this discussion, but stating that everyone else is dumb or can’t adopt these ideas is not nice at all, and it becomes just a case of arrogance on your part.
Albert; Albert Kallal: but stating that everyone else is dumb or can’t adopt these ideas is not nice at all, --Hey Man! WATER4GAS Again? By the way, what is your ultimate advice for ACCESS developer regrading Runtime Deployment Issues as of this time? Inno? Sagekey? Half Cooked Solution and not applicable in real Combat! Please share your true talent regarding deployment issue! POST IT HERE NOW, SO..SO..SO MANY NEED YOUR HELP!
> Albert, can you tell me about "VPC" you're referring to? VPC is a free virtual download from MS that allows you to run “multiple” copies of an os (I am running Vista on VPC on my laptop for example). I also have windows 3.1, 98 se, windows 2003, and a bunch more that can all run on my laptop. Memory permitting, I can run as many as them at the same time. One can even network those imaginary computers. I even setup a server for testing of SharePoint, So, VPC is your ticket for testing. VPC is a possible solution to run multiple versions of MS access, but VPC requires you to install a whole operating system. Since you have to install a whole operating system, then it not a very lightweight solution for deploying ms-access on many computers. For development purposes, VPC is a must have item in your tool box. VPC allows you to create throwaway virtual pc’s that you can use for testing of your installs. So I don’t recommend VPC for installing on machines, but it is an must have for developers. Albert D. Kallal
Edmonton Alberta Canada
> Please share your true talent regarding deployment issue! Again, there is not a need for you to be so condescending here. Lighten up a bit, ok? Ms-access has always been part of office, and it never really was designed for independent installs. There no secret fix here. However, the Sagekey solution is what I would suggest at this time and it really is quite a good solution.
Albert; "If you really want the smart solution then there are so many solutions or ideas. But If you dont want, then there are also many reasons". VIVA Postgre or MySQL as Ms Access Backend!!
Albert Kalal: MS says that Access is a professional solution. They might be right. But it's a solution with a non-professional and buggy PDW. So, in the end, is this professional?
SageKey = professional tool for MS Access
MS = ?
Thank you Albert. Something else that's been bothering me... you think Erwin might perhaps have a personal investment in Thinstall?
>MySql as a acces backend. Sure, that is a great solution. I rather think my free SharePoint idea is even better since then you don’t have to purchase a computer and then setup a “sql” server on it. Why purchase a whole computer and spend all that time installing MySql when you can use office live for free? The ability to use free SharePoint allows my applications to become multi-user over the internet in different locations without having to setup a server. This sharepoint is an amazing new feature that opens up a lot of doors for me as a developer. However, it really depends on your needs. If you don’t need a separate new server, or you are willing to spend the time to setup a server and install the software then there is quite a few free sql servers available. Those choices range from the Express editions of sql server right on down to your suggesting of Postgres. All of these server data engines work well with ms-access, and this just means we continue to have more and more choices as developers on how we going to use ms-access with a back end data system. Being able to use Postgres or SharePoint shows that ms-access continues to become more flexible as a developers tool. Albert D. Kallal
To MammAfrica; MammAfrica: Something else that's been bothering me... you think Erwin might perhaps have a personal investment in Thinstall? I don't have stake in VMWare/Thinstall. Me and my clients are very happy with thinstall deployment strategy. It's really a ALL-IN-ONE solution in deployment specially in ms access runtime. Which wasn't solved by MS til this moment in time. Even SAP use the tool, US Armed Forces, GE and ever expanding. I started to develop in delphi for one reason; deployment Issue. But then I found thinstall, so goodbye delphi. I can now distribute my finish product in a single stand alone EXE much more than delphi can. This is a true confession and sharing my friend about Access runtime deployment problems.
albert; Ken Getz, Litwin,Gunderloy abandoned ACCESS? why?
>Me and my clients are very happy with thinstall deployment strategy. Sure, but that is not a affordable solution for most people here. Likely in your situation you were able to justify using such an expensive tool. And your likely distributing lots of copies and thus once again it not really an expensive solution in your case. >abandoned ACCESS? why? I really have no idea, but then why don’t you go ask them? How could I know? However, if you in the habit of such questions, then whey did you drop Delphi? Why do some people drop Java these days? Anyway I think these types of questions are starting to make this post way off topic… Albert D. Kallal
erwin leyes:
"albert; Ken Getz, Litwin,Gunderloy abandoned ACCESS? why?" See the first posts of mine in this thread.
Comments: (loading) Collapse