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.
Related
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.
I have an old ASP Classic site which connects to a SQL Server database which uses a Linked Server to access a Microsoft Access database via OPENQUERY in a view (!), like this:
A Linked Server is configured to connect to the Access database using Microsoft.ACE.OLEDB.12.0
A view view_requests retrieves the data from a table in the Access database:
SELECT *
FROM OPENQUERY(MY_LINKED_SERVER, 'SELECT * from Requests') AS Rowset_1
The ASP Classic page retrieves the data:
Set getRequests = dbConnect.Execute("SELECT * FROM view_requests")
Since moving it from a Server 2003 to a Server 2012 machine it no longer works.
The error given on the ASP page is:
OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "MY_LINKED_SERVER" returned message "Cannot start your application. The workgroup information file is missing or opened exclusively by another user.
But I have a feeling this is misleading for several reasons. The error seems to occur in lots of different scenarios and none of the posts I've found represent mine exactly. The main thing to note is that the view works fine and I can therefore access the data via SQL Server, which to me suggest it's not an issue with user mappings and so on, but I may be wrong. The problem occurs when connecting via the ASP Classic page. We've tried using both .mdb and .accdb formats.
Any suggestions on what I can try would be much appreciated. Thanks!
This sounds like it might be a permissions problem (I was going to say 'access' but that came out confusing!).
How are you controlling access to the SQL database? Is it Windows Authentication or using a SQL logon? If it's Windows Auth, then you need to give either the calling user's (if using Impersonation on the web site) or the Windows Identity that ASP.NET is running under access to the Access database file. If using a SQL Logon then you need to give the Windows Identity that SQL Server is running under that access.
The error is not necessarily accurate and from my experience, it probably is not. The account that SQL Server is running under (NOT the SQL Login) must have full permission on the folder where the Access file is located. Another possibility is that the linked server is not using the correct ACE driver, or it is not installed. If using SQL Server 64 bit, you'll need the 64 bit ACE driver.
It seems the issue was that we were incorrectly mapping the SQL user to the remote server (Linked Server > Properties > Security), even though it seemed we'd tried every possible combination of settings under the sun! So it seems the original misleading error was trying to tell us that the user didn't have the permission.
It is currently working with the Local Login mapped to Admin, the default Access database user which has a blank password. Under For a login no defined in the list above, connections will: we have selected Be made using the login's current security context.
Thanks to AVG for pointing me in the right direction.
I will try make this question clear as possible.
I have not found solid help on google really or anywhere else.
To make it short and simple.
I have a vb.net project in which i want two databases.
A local access database which must be created within the project at design, meaning at publishing and then installing this program to another user it must automatically create an acccess database on that user's computer,sync it with a SQL remote server and copy all records at first time run to the access database. The access database is used when my worker is on site and there is no connection to the remote SQL Server database.
Upon achieving connection to the remote SQL Server database at e.g. the office, the access db must update the SQL server database,compare the two databases and copy any new records in the local (Access Db) to the remote sql server and vice versa.
Hope this is clear enough?
Thanks for any help
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
I have an old Access project (.adp) that was tied to a SQL Server database using integrated authentication. The .adp is only used this time of year. Since its last use, the SQL Server has been virtualized and patched to current. When I try to open the .adp, it gives me a "Cannot generate SSPI context" error. I got this with another .mdb and just remapped the linked tables through ODBC with a SQL Server login (integrated authentication is not a requirement). However, with this .adp file, just about all the options are greyed out. For example, Linked Table Manager and ODBC Database buttons are greyed out. I can't see any tables, nor apparently link or import any. Is there a way to remove integrated authentication from an .adp project? Or can I convert the database to an .mdb (exporting objects appears greyed out as well)?
NOTE: This is a limited use database with few users on its way out, so I'm very open to "creative" workarounds that don't require me rebuilding the whole thing.
Please, review the following:
Check that SQL Server allow integrated authentication
Your machine (where you open the adp project) and the server are both in the same
domain.
That error is typical when the client machine belongs to another domain or not belongs to any domain.