


The new developer tools force you to create an MDB, and then when you go to compile the final build, you hit a checkbox for "distribute runtime" and it lumps the runtime installer together with your MDB. The runtime installer was maybe 4MB or 5MB large. Here's the problem: I used to be able to distribute the runtime installer as a seperate installer. I wasn't necessarily looking for the actual software-although the download shows me the files I need to generate through the developer tools. I think Microsoft has bigger fish to fry though, so I suggest we all put down our tasers. It also lacks a little thinking to do so in a public forum and using a Canadian government's website to do so. He was however wrong in encouraging people to use the runtime installer seperately from the program it is being distributed with. Officially, "TheQuestioner" did nothing wrong in distributing the software because he did so according to the license. I did mention that we participate in the MSDN program (we are a Microsoft Partner), which gives us access to nearly every Microsoft license imagineable (including the developer tools in question). He was intending to be helpful, although his execution was wrong. You are right, although I think a little rough on "The Questioner". TheQuestioner (Programmer) 7 Nov 05 20:38 If anyone knows, I would greatly appreciate it! If not, is distributing the runtimes with the MDB's the ONLY way to do this? I guess what I'm asking is, is it possible to find a download for JUST the runtime installers for 20? However, I do not want to include the runtime with my MDB's, I just want a standalone runtime installer. From what I understand, I can use a "package wizard" to compile the runtime installer with my MDB's. We participate in the MSDN program, and I downloaded "Access 2003 Developer Extensions" and "MS Access XP for Developers". Now that we have moved to Access 20, I do not know where to get the runtimes to include with our program. For years we have distributed MS Access Runtime as an option in our program's install (we use InstallShield). My company develops an application which uses (in part)many different Microsoft Access MDB's to run reports.
