May 7, 2013 at 8:51 pm
Hi,
I have an access 2010 adp linked to SQL 2008 r2.
Another system we use which also has a sql backend hold employee id's and names . I want to use this employee data in our main sytem so I've set up a linked server - and a view based on this.
I've given db users select permissions on the view but they're receiving the error message: "<access db name> could not log on to the server. Verify that the log on information is correct."
Sql is set up to use windows authentication. The linked server is impersonating my log in.
Any ideas on how to resolve this?
Thanks,
Peter
May 9, 2013 at 4:59 pm
Can you clarify what you mean by a linked server? Is that being done at the SQL Server level so that the view shows up in the SQL database where your application tables are stored? Or are you doing something with ODBC links? I should also add that the ADP model is not supported in the current (2013) version of Access, so you may want to rethink your architecture if this is a new development.
Wendell
Colorful Colorado
You can't see the view if you don't climb the mountain!
May 9, 2013 at 6:53 pm
By linked server I'm on about a linked server object set up on SQL Server with:
Exec sp_addlinkedserver N'<server name>', N'SQL Server';
EXEC sp_addlinkedsrvlogin '<server name>'
The view is set up on sql server with:
SELECT EmployeeCode, LastName, FirstNames, WorkAreaCode, LocationCode, DepartmentCode
FROM <server name>.<dbname>.<schema>.<table> AS EMPLOYEE_1
I've given select permissions on the view to a bespoke database role.
I've set up one user with login permissions on the remote server (as a test).
within the adp the view is visible similar to a linked table but it just wont open up.
I hope that clarify's things a little - my goal in all of this is to have the employees table from one system visible on the other so we only need to maintain the records in one place.
As for the adp's being deprecated; yep it's been on the cards for a while. It's days are numbered. There's a big job ahead changing formats.
Thanks for your help,
Peter
May 11, 2013 at 2:55 pm
Since you are using Integrated Security, as long as you have permissions set both on the linked view in your local database, and on the view in the remote database, I would expect you should be able to open the view in the Access Data Project. As a test you could try linking the view into an empty .mdb database using ODBC, and see if you can open it that way. If not then I would expect to to be an issue with permissions at the SQL level. You could also try opening an ADO connection to that view in the remote database and see if that works.
Wendell
Colorful Colorado
You can't see the view if you don't climb the mountain!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply