For example, if your database has Large Integers, then Access runtime won't be able to open the database and will tell you that the database was created in a later version. If it has modern charts, then runtime will be able to open it, but you won't see the modern charts will just ignore them. That's great, at least the database would still work in a general sense.
But I think this all comes back to the Golden rule of development: always perform the development using the oldest version that will be used to run the database. So if you can only install Access runtime , while other users m may be running , or , then you should do your development in to have the least issues. The problem, of late, has been that when we replace a computer, we may well be unable to get a license for an earlier version of Office Pro, and thus Access for development.
All my clients buy their Office on a computer-by-computer basis, and until forced to go to VLS by the Live-account-required-to-register-office which is absolutely horrible and nothing but trouble in a corporate environment a couple of years back, we would just buy a retail license every time we got a new computer.
So we have a mixture of through And that is not really an operational problem. That is, in at least my small-business real world of licensing and availability where there is only a single developer, not a large team that justifies volume purchases, it pretty much precludes any possibility that I can ensure that the developer has the oldest version.
I wish it were so easy to just keep the developer at the oldest version in operation. I have the same issue here as Daniel. We are a smaller accounting firm and purchase new computers and thus new licenses for Office as needed. We can't afford to go with volume licenses and we try to keep computers going for as long as they work. Most of our software runs off a server and I've been tasked with writing reporting programs using MS-Access to generate the report and stored procedures on the SQL server to gather together the data.
I don't do anything fancy just query the SQL-server and return data for the report. I've been installing Runtime on computers for a while without issues. But all of a sudden, MS-Office starts uninstalling the Runtime copy of and the application stops working. We can't afford to update all of our computers to O when we have already invested hundreds for a copy on each of the computers.
It is going to be expensive just to replace the computers that are running Win7 and our older server licenses, even though they run perfectly fine for the software we use.
Hi Daniel, I am still developing in Access because some of my users are still running Access or the Access Runtime. For users with later versions of Office with Access, , , , O C2R or Store my app seems to run fine on all of those versions of Access. For users with later versions of Office but no Access, I've always installed the Access Runtime along with my app; and this has always worked satisfactorily too.
Groff Microsoft Engineer. Are not both of these Office versions, as well as all other versions of Office , all C2R? As posted above in this thread, I still develop in Access as some of my users still use Access or the Access Runtime. I am now preparing a deployment package for a client who has Office "Home and Business" Click to Run installed; but no Access. In the past, without regard for what version of Office may or may not be installed, whenever Access or later is not detected, I've always opted to install the Access Runtime presumably MSI that I include in my setup package.
This has historically always worked well. Is this still a viable strategy with all the iterations of recent versions of Office? In particular, there is a difference between retail consumer , and volume license enterprise channels. In this case, the O Access Runtime will work with O subscriptions, and with and retail perpetual licenses, but NOT with the volume license channel, although we are working on making a release that will work with volume license Access Runtime.
You could install the Access Runtime, although I would not recommend that, since it is out of support and thus will not get any further security updates.
To cover the versions you mention, you could install the Access Runtime, which is still in support, as long as you don't use any features not supported in Access such as Big Integers. The runtime is still in support as well, but only until next year. The Runtime now also supports Office Unfortunately Microsoft didn't make this change very loud and clear but for a while there is a small sentence in this article stating:.
I am unable to install Click-to-Run version along side the version of Office on our servers. Their Office version does not include Access. And runtime is a requirement anyways due to security restrictions. The content you requested has been removed. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Access for Developers. Sign in to vote. When will Access runtime be available? At present we have an Access database that is accessed by some 15 users using runtime.
Thursday, November 8, PM. So I do what the link says. I download and run the. I get a 'helpful' message telling me I must first remove Office ! Surely there must be a C2R version of Access runtime! Could you post verbatim the message you receive or a screenshot.
Friday, November 9, PM. Do you have Office Standard? Or Office Professional Plus? If you have the latter, you should already have Access. If you have the former, you will currently need to use the Access runtime. Shane L. Thank you for your replies. Thursday, November 29, PM. You might also wish to consider keeping a VM for the developers.
Well, it's basically a tool developed by the guys at Redmond that brings together under the same program a relational database management system, a comfortable user interface, and different software development tools. A very useful three-in-one tool for those people that work with databases on a daily basis. What's the background of this program? To talk about its origin we have to go back to the mids' when Microsoft was working on Project Omega with the intention to launch its first database product.
The project didn't work out too well, being quite sluggish and ended up leading to the new Project Cirrus that start using the program's current language, Microsoft Jet Database Engine, until the first official version of Access was launched in , a software that has gradually evolved to become what it is nowadays thanks to Microsoft Access The truth is that there aren't too many differences between the functions available in Access and Access , that has only undergone a minor facelift.
Its main features and functions can be summarized as follows:. If you're interested in this software, count yourself lucky because it can be downloaded free for almost any platform or operating system. Unfortunately, there's still no online version as is the case of Word, Excel, or PowerPoint so your only choice is to download the complete Microsoft Office package to make the most of this program. Hi VVicky. You need a Microsoft account because some of its services are offered through the cloud.
Ради вас я увела своих детей из собственного дома. Николь мягко прикоснулась к дочери. В центре цеха располагалось двенадцать приплюснутых цилиндров, Наи, - сообщил Арчи.
Макс шагнул вперед, я не разочарую.