Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

MS Access front end to SQL server 2008R2 backend Expand / Collapse
Author
Message
Posted Wednesday, February 27, 2013 6:13 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, February 28, 2013 2:15 AM
Points: 2, Visits: 5
Hello,

We use MS Access 2010 to obtain data from our Sybase\SQL anywhere database.
The name of this database is called "e2i".


We are moving to SQL server 2008 R2 and have converted our database to work on the server.
The name of our this database has been called "Radan".

I have setup a DSN connection on my client to connect to the "Radan" database. The tests show they are successful.

When I go to run MS Access to connect to the "Radan" database to extract the data I get the following message I am presented with SQL server login and must enter loginID and password.

After I enter the login credentials I get the following message:

"Could not execute query, could not find linked tables... invalid object name".

I then use Linked Table Manager but again the SQL server login appears and the username \ password must be entered for each dbo.

Is this the correct way to get MS access frontend to work with the new SQL server database?

Thanks,
Frank

Post #1424484
Posted Wednesday, February 27, 2013 9:35 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Yesterday @ 1:48 PM
Points: 601, Visits: 6,481
Hello there! I believe the solution to your problem should be in the External Data tab; use the ODBC Database option, just a bit over from the Linked Table Manager. You should get a menu with two options; select "Link to the data source by creating a linked table" (or, if you just need a copy of the data and not the ability to modify the SQL tables from Access, use the first option). In the new window that appears after you hit OK, use the Machine Data Source tab, which should have a list of DSNs on your system; pick the one you created for the database out of the list and hit OK, and you should get a list of all of the tables in your SQL Server database. Click each one that you'd like to link into Access and hit OK, and that should get everything imported.

Keep in mind that the schema names from SQL Server will be preserved (so anything in the dbo schema will be dbo.tablename, for example), so you may have to do some renaming if you have existing procedures that reference SQL tables. Also, if you're creating a copy of the table rather than linking directly to the table, you'll have to re-do the copy each time you need a fresh version; Access unfortunately doesn't have anything to make routine copies, to my knowledge.




-
Post #1424603
Posted Wednesday, February 27, 2013 9:55 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, February 28, 2013 2:15 AM
Points: 2, Visits: 5
Thanks for your reply.

When I follow your steps the following error appears:

Access database engine could not find the object 2DBO_syscurconfigs". Make sure object exists and that you spell the name correctly. If it not a local object check your connection.

Is the import\export wizard of any use for linking to my Access db?

My Access database was created in Visual Basic to extract data from the backend database.

Thanks.
Post #1424624
Posted Wednesday, February 27, 2013 10:59 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Yesterday @ 1:48 PM
Points: 601, Visits: 6,481
Hm, that's unusual. From what I can tell, syscurconfigs refers to a compatibility view used for backwards compatibility with SQL Server 2000 (source: http://msdn.microsoft.com/en-us/library/ms177502.aspx). Seems as though it's dynamically constructed when a query is fired at the view, so Access probably can't handle the fact that it won't exist when you're trying to link to it, though I'm not certain if part of your application will need to reach that view or not.

The import/export wizard in SQL Server could well handle your problem as well, though. There is an issue with it in that you wouldn't have real-time data from your SQL Server database; however, if you only need occasional imports and processing of that data, it would definitely work. You could use the wizard to set up a SSIS job to export data from SQL Server into Access, then schedule that package to run at regular intervals, if that's a workable solution in your environment.




-
Post #1424654
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse