I have developed a access 2007 database that is hosted on the clients server. They input data 24/7 in house, and enjoy the fast speed of the local connection. However, they are now wanting to view this data on a mobile device. I would like to be able to create a new Access 2013 web app, and have my current access 2007 database transfer data to a hosted server somewhere, where the access 2013 web app will run from. There won't be any need to add/edit/delete data from mobile, just view, so that saves me a lot of trouble with having to convert all my vba. I just have no idea how to go about this, or if it is possible. If I use a hosted sharepoint server, can I add my web app there, and be able to transfer data to the server to view?
Unfortunately Access 2013 web uses SQL Azure, and starting with Access 2010 is when support for Azure was introduced. I not at all sure you can thus use Access 2007 to connect to a 2013 web database (you should be able to use 2010 or 2013).
I think in this case you might consider just building a simple asp.net web site and then have Access 2007 send some data to that site (assuming the site allows external ODBC connections – these are becoming harder to find these days).
As I alternative I suppose you could upgrade to Access 2013, and for existing desktops deploy the FREE 2013 runtime. This should in theory allow you to keep your existing application, and also connect to the 2013 web application you publish. You have to sort up the users permissions here.
So while the Access client(desktop edition) can link to published Access web applications, I don't believe that Access 2007 can be used since it does not have support built in for using SQL Azure like 2010 and 2013 does.
Related
I have here a specific application I am forced to use. This application uses Access as data storage.
This application is older and was once developed for Office 2013. Our company computers have now Office 2016 installed, with Access 2016.
After the installation of Access 2016 this application stopped running. It hangs immediately after start.
So i installed Access Runtime 2013 and application first worked fine. But as soon as I open Access 2016, there is a repair run installing something in the background and application again stopps working. After executing Repair on Access Runtime 2013, it works again until Access 2016 ist again opened.
After checking the dump of this Application I see that after running repair of Access 2013, Office15-DLLs are used. After starting Access 2016 and repair run, Office16-DLLs are linked and application stops working.
All those repair runs take minutes, so they are very annoying, as I often have to switch between both applications.
Is there any other / better way to handle it? I tried to set Runtime 2013 into the PATH of my application, no changes. Can I somehow force the application to use Runtime 2013 instead of Access 2016?
Thanks!
I'd like to upgrade my application to use the newer Access 2007/2010 database engine. It currently stores its data in a Jet 4.0 (MDB) database. My application is written in Delphi, and it uses ADODB (ADO classic) to interact with the database. I'd like to upgrade the database engine from Jet 4.0 so that I can offer better encryption options.
I changed the connection string in my application to use Microsoft.ACE.OLEDB.12.0 and despite a few hiccups, the conversion went amazingly well! Impressive backward compatibility.
I also distribute my application in a Wine bundle for Mac users. I'm running into a few problems with running my application under the Access 2010 Database Engine on Wine (1.4-rc1). Strange access violations appear. When I install the Access 2007 Database Engine on Wine instead, my application works great. Just as good as with Jet 4.0. So it appears that the Access 2010 Database Engine isn't quite ready for Wine. Bummer!
The problem I'm running into is that if you have the Access 2010 Database Engine on your Windows machine (such as when you install Access 2010), when it creates a new database it encrypts it using a higher form of security that is incompatible with Access 2007. Users of my application couldn't share their database between their PC and Mac (i.e. via Dropbox) since they would no longer be compatible.
In Access 2010, you can set an option for it to "Use legacy encryption". This option causes Access 2010 to create new databases using an encryption that is compatible with Access 2007. This option sets a registry key "CompatMode", and the Access 2010 application must take a different approach to creating new databases in this case.
My question is: How can I programmatically create an encrypted database that is Access 2007 compatible from the Access 2010 database engine? If the Access 2010 application can do it, how can I? I'm aware of two techniques for creating an Access database: 1. via DAO (DBEngine.CreateDatabase), 2. via ADOX (Catalog.Create). I've been trying various approaches to these two techniques, and can't come up with anything that creates an encrypted database that is Access 2007 compatible.
I have a Access 2003 database that I want to store in source control on TFS2010. I'll be using the Team Foundation Server MSSCCI Provider 2010. Are there any rules for which versions of Access can create a database from that source? It's possible that Access 2010 and 2007 will be used to edit the source control. I'm curious as to if I should limit the versions of Access touching the source code to just a single version of Access.
The site of MSSCCI states to support Access 2007: http://visualstudiogallery.msdn.microsoft.com/bce06506-be38-47a1-9f29-d3937d3d88d6
On the same site, two other references from users can be found. One is stating that this version also works for Access 2003. Somebody else is experiencing that this version of the MSSCCI does not work for Access 2010.
A save bet would be to start your efforts with Access 2003, or if possible better with 2007. At least do an experiment with saving some 2003 stuff and opening it again with 2007 and vise versa. In time, I guess that support for Access 2010 will show up and you can continue from there on with newer version.
I have an Access database in source control on TFS that I need to pull down onto another machine (XP, Office 2007). I have the Team Foundation Server MSSCCI Provider 2010 installed and I can successfully see the source. However, when I try to have it created it fails, giving me this error:
Failed to create a new database on a Team Foundation project.
Any idea what I've done wrong on this machine?
I think the solution to this was that I had sent the database up to TFS from Access 2010, but was trying to pull it down to another machine with Access 2010. I thought the two versions shouldn't matter, but sending it up to TFS in Access 2007 and bringing it down in Access 2007 and Access 2010 appeared to work.
I have a MS Access 2007 database and a WSS 3.0 site (neither of which I am very experienced in). The database is currently stored on a shared drive with users remoting in to work with it. In an effort to improve usability and performance, I want to host this db on my WSS 3.0 site. Is this feasible? I need to be able to access and edit data using forms, as well as run reports, all through the UI of the sharepoint site.
You can host an .accdb on a WSS 3.0 site, but users will need Access 2007 to open the database. See this article for basic info: http://office.com/redir.aspx?assetID=HA010131469.
If you want to host Access on Sharepoint and let folks who don't have Access use the database, you need Access 2010 and Sharepoint Server 2010: http://office.com/redir.aspx?assetID=HA010356866.