Hi let me start of with saying I have Zero Experience with SharePoint. I have tons of experience with MS Access and SQL Server.
Normally when i need a Data entry front end i'll go for MS Access, but in this case most (probably all of my users) do no have MS Access so a standard MS Access Desktop App is useless.
I have heard that MS Access Web App can be published on to SharePoint, and then Sharepoint can be shared with our users so that they can enter the data.
Now through doing some reading up. I know that you can create a MS Access Web App through sharepoint then design your forms on MS Access and publish them, and the data will be then stored on to SQL Server of the Sharepoint. I hope I have that correct.
I need to be able to access that data through SSMS infact it will be so much better if I can just create the sharepoint app pointing to my sql server.
It would be really helpful if you could offer some guidance on this.
Create MS Access Web app on sharepoint (With data going into another SQL Server)
Craete MS Access Web App on SharePoint (With data going to the SharePoint Server) - but in this case I need to be able to access the database, and be able to add triggers and constraints.
This might be a very stupid question, but I have no idea how Web App and SharePoint work and I currently have no access to SharePoint so I cannot test. I am basically researching before going ahead and asking for SharePoint from my company.
Related
I am creating a website, using mostly html and some php pages, now I have to create a database and connect it with my website, for log in and requests, my question is what database should I go for, is Microsoft access good enough? or sql server or phpmyadmin? the website isn't large, it might get 6 requests per day, I am not a professional programmer but I know a few things about programming, please help
I am an developer in Access. Access technology is a Windows application, not intended for web applications. It is not a back end database which is what a web server needs behind it. The SQL Server - Express Edition (free) would be the product from the Microsoft family. Of course there are other suitable shareware products out there, probably the best known being MySQL.
When the requirement is for internal needs, not public facing, but the users are geographically separated; then Access (and other Windows Applications) are platformed on a Remote Desktop Server (aka Terminal Services).
The other alternative to building your own web application is using one of the database centric web services: Soho, QuickBase, Knack, etc.
I have an Access Database (accdb) with relationships (and linked tables) that is incompatible with Access Services. It is currently saved locally but I have it on a SharePoint site as well.
I also have created an Infopath form that queries the local Access Database for different fields, and is able to submit data back to make changes to the tables, etc.
I now want to shift the connection to the database that is saved on the SharePoint site. I went to modify my Main data connection (the locally saved Access Database), changed database to point it to the access database that is on the SharePoint site. It definitely recognized that it was an Access Database, because it even showed me my tables and queries and asked me to select a table. But when I do so, it says there is "An unspecified error occurred while attempting to
connect to the data source. Microsoft Office InfoPath supports only MS SQL
Server and MS Office Access databases. Please check the connection to ensure
it uses one of these two databases."
Would any of you know how to resolve this error, without having to set up SharePoint Lists to connect back to my Access Database (I don't see how this would allow the initial querying of the data that my InfoPath form has to do).
Thanks in advance for your help.
Make sure your database it Access 2013 or older, older versions of access aren't supported in SharePoint to modify.
I would create with Access 2016 a database that lives in the SharePoint Data Connected Library and connect to that.
I have built a CRM for my company using MS Access 2016, and we are looking to be able to use it remotely. I have currently split the database and have the back-end residing on our company server/shared drive. As I see it, we could put the back-end on SQL Server, but that would mean finding a way to host it. We recently moved to Google Apps for Work and I have been looking at the Google Cloud platform (e.g. Cloud SQL), but I don't know if it will integrate nicely with MSSQL. There's also Sharepoint, but we are are having difficulty even finding it to buy on Microsoft.com, and are trying to move away from Microsoft Office products anyway.
What would be the most stable, cost-effective, and fastest way to allow our employees to use our Access DB remotely?
My suggestion would be to migrate the database into SQL Server as step one. Then step two host the database in Microsoft Azure using the SQL DB service.
You can find more details and pricing here: https://azure.microsoft.com/en-us/services/sql-database/
Be sure you check the single database pricing. Unless you want the elastic scaling and performance.
I'm not sure about the cost part, but the fastest and most stable (IMHO) would be to use Remote Desktop. Either to a user's workstation or to a server set up for it.
We have migrated our backend to SQL Server from MS Access for obvious reasons. Our users access the front end off a VPS Hosted in the cloud. Connection string ODBC. It is robust and fast.
we are currently using a VPS. Looks cheaper and easy to access ;
https://clients.databasemart.com/aff.php?aff=275
I have an application that currently uses Microsoft Access 2013 as a front end with SQL Server 2012 as a back end. When in the office, that's fine for the users, but some of the users need to be able to access (no pun intended) the application from other sites.
Is it possible to publish the Access front-end to the web while retaining the connection to the back-end tables in SQL Server, and allow the access from SharePoint as an alternate means of getting to the application?
There are firewall issues to contend with, so I was hoping that we'd only have to worry about a firewall opening between the SharePoint server (network A) and the SQL Server (network B). I'm sorry I can't be more specific than that.
In my project I need to publish an Access database into Sharepoint. I need to add a web form into it. Is it possible to add a WebForm that can be shown in the Sharepoint site, using ODBC(Database from SQL server on local machine)?
I can connect to that database and edit records in it. But I can't make a form with that web icon on it. Is that even possible to publish something from Access to Sharepoint using local SQL server and make a form to show data from it?
I found something like that:
I totally missed the fact that this was a web app. Access web apps
work with SharePoint, no other data source. That's true for Access
2010. But in Access 2013, there is a hybrid solution possible: Access Client + Access Web + SQL Server. It's still very new and not
common yet, and unfortunately there isn't a migration path from Access
2010 web forms to Access 2013 web forms. You have to build the web app
from scratch. But it's a better platform than Access 2010 offered.
that means i should use access 2013 ?
I am no expert and can't test my ideas, but I read that if you publish an Access db with Access tables to SP, Access tables will be converted to a SQL Server table by SP. Perhaps you could then delete or rename the SP created table on SP's SQL Server and create a view with the same name which points to you table on the other server ?
Have a look at the SP site: https://sharepoint.stackexchange.com/q/104005