Connection from Access to SQL Server does not show ALL tables

I have an ODBC connection to a SQL server database and for some reason I can
see some of the tables but not all of them when i try to establish a link to
a table.
any ideas? Is there such a thing as a hidden table at the SQL server end ?
Steve
No, there is not. I'd check your permissions to see if you have
adequate permissions for the ODBC login/DSN you are using to connect,
and if that's not it, check the syntax in your code for typos in
names, etc.
--Mary
On Fri, 3 Feb 2006 09:50:21 -0800, "Steve"
<Steve@.discussions.microsoft.com> wrote:

>I have an ODBC connection to a SQL server database and for some reason I can
>see some of the tables but not all of them when i try to establish a link to
>a table.
>any ideas? Is there such a thing as a hidden table at the SQL server end ?

Connection from Access to SQL Server does not show ALL tables

I have an ODBC connection to a SQL server database and for some reason I can
see some of the tables but not all of them when i try to establish a link to
a table.
any ideas? Is there such a thing as a hidden table at the SQL server end ?
--
SteveNo, there is not. I'd check your permissions to see if you have
adequate permissions for the ODBC login/DSN you are using to connect,
and if that's not it, check the syntax in your code for typos in
names, etc.
--Mary
On Fri, 3 Feb 2006 09:50:21 -0800, "Steve"
<Steve@.discussions.microsoft.com> wrote:

>I have an ODBC connection to a SQL server database and for some reason I ca
n
>see some of the tables but not all of them when i try to establish a link t
o
>a table.
>any ideas? Is there such a thing as a hidden table at the SQL server end ?

Connection fails in linking SQL Server 2005 tables into Access using DAO 3.51

Hi,

I have an app that creates and attaches tables from SQL Server into an Access mdb using an ODBC link from VB6 using DAO 3.51 on Windows 2000. Recently I upgraded to SQL Server Express edition and tested it. It worked fine against the Express Edition. So, I installed SQL Server 2005 Standard Edition on our Server hoping that they operate identically. How wrong one can be! the same code that worked against Express Edition does not work on Standard Edition.

It is strange that the App works for about 5 seconds which attaches about 38 tables and after that the connection drops and I have a hell of a time to get the rest of the tables linked. The error that comes up is:

Connection failed:
SQLState: '01000'
SQL Server Error: 10060
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.

The PC that I am using to connect is in a different domain to the Server where the SQL Server database resides. I thought that domains might be the reason. But even joining the PC to the same domain as the server still does not work and behaves the same. So I do not think it is a domain related issue.

I have also looked at the SQL Server and database configurtaions. I cannot see anywhere any specific time out of around 5 seconds. Even the time out through the SQL Server ODBC driver is set to 30 seconds by default as far as I know. So, it looks like there is a time out somewhere but I am absolutely confused as to where this 5 second time out is comming from.

I also thought permissions on the database or tables might be the issue but after looking at the database and table permissions, they all look OK. The user has prettymuch the same access as the SA on the database.

Has anybody came across this problem? If so, I appreciate if someboday can give me a hint as to where I can start.

Thanks,Hi

welcome to the forum :D

Using VB6 to programmatically create linked tables between Access and SQL Server 2005 using DAO 3.51 seems a slightly odd way to go. I presume there is good reason?

Anyway - can you manually link the tables?|||Hi

welcome to the forum :D

Using VB6 to programmatically create linked tables between Access and SQL Server 2005 using DAO 3.51 seems a slightly odd way to go. I presume there is good reason?

Anyway - can you manually link the tables?

Hi,

Thank you for your reply.

Our application is a reasonably complex one. So I will not bore you with the details but if you want I can fill you in outside of this forum. Rest assured that there is a good reason for doing this.

Anyway, The tables link properly if I just open an Access MDB, use the same DSN and select all the tables. However, when they are linked from within our App, they fail. Any ideas?|||Hi,

Finally worked out what was causing this problem.

After looking around the application event logs on the server, I noticed that ISA server was not letting the application to connect. It was saying that the connections for my PC have exceeded the maximum allowed.

I looked at the ISA server and as I expected, there was a maximum of 40 for TCP connections. That is why the application was managing to connect 38 tables (we had two other connections within the app to the SQL Server Database). Once I increased the limit for my PC's IP address, everything went back to normal. So it was not a timeout issue.

They have set this limit to prevents attacks and I can see it working if people use fixed IP addresses. But if DHCP is used, the only other option is to increase the limit globally which goes against the initial gaol of having the limit in the first place.

Thanks

connection an access db to sql express backend

can someone advise me as to what i have to do to connect an access frontend to an sql server express backend db on another server.

can i somehow link the tables so a user can enter in data in the access db they are familiar with but it will actually go into sql server.

please help

Hi,

you can either click right in the tables area and add a linked table using an ODBC connection or use a ADP project which can directly access the objects of a SQL Server database. But it is important that you enable remote connections on the SQL Server side using the Surface configuration. See the screencast on my side for more information.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Connecting via Radio Link

Could somebody tell me as to what configuration changes has to be made in the SQL Server 2000, if I want to connect to a table in the database using Internet options, i.e., I have the SQL Server running on a machine which uses a real IP address, and I want to connect to it (SQL Server)using DSN from another location. In the 2nd location, I use internet using dialup/DSL/Cable Broadband.

--
The following error is shown, when I try to connect to the SQL Server using SQL Server authentication using login ID and password:

Connection failed:
SQL State:'01000'
SQL Server Error: 10060
[Microsoft][OBDC SQL Server Driver][TCP/IP Sockets]ConnectionOpen[Connect()]
Connection failed:
SQL State:'08001'
SQL Server Error: 17
[Microsoft][OBDC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
-----

Thanxs in advance to anyone who can help me solve the problem.You can use the Client Network Utility.

Go To Client Network Utility. Go to Alias Tab.
Click on ADD. Provide a Alias Name, and the Server IP address or the URL as Server Name under the Connection Parameters Section. (Netowrk Libraries can be Named Pipes)

Thats it. When you go to Enterprise Manager, you can register that server by its Alias name.

Connecting via ODBC

Hi all,
Hope you can help, I am trying to link to some data tables into Access via
the ODBC connection. It worked for me before but i have had issues with my PC
and now i get this message:
[INTERSOLV][ODBC SQL Server driver]Communication link failure.[INTERSOLV]
[ODBC SQL Server driver][SQL Server]ct_connect(): directory service layer:
internal directory control layer error: Requested server name not found.
I suspect this will be a hard question to answer but I'd appreciate any input.
Cheers
Dave
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-connectivity/200801/1
This is a pretty general error. It could be caused by your network, or by
SQL Server settings. You didn't say how long ago it worked. Yesterday, or
last year? If yesterday you may have changed something. If last year, it
could be lots of things.
You didn't say what version you are using. If SQL Server 2005, check out the
connectivity tutorial which was designed to help users with just this
problem. http://msdn2.microsoft.com/en-us/library/ms345318.aspx
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Suttd via droptable.com" <u25367@.uwe> wrote in message
news:7e0eab8790a4c@.uwe...
> Hi all,
> Hope you can help, I am trying to link to some data tables into Access via
> the ODBC connection. It worked for me before but i have had issues with my
> PC
> and now i get this message:
> [INTERSOLV][ODBC SQL Server driver]Communication link failure.[INTERSOLV]
> [ODBC SQL Server driver][SQL Server]ct_connect(): directory service layer:
> internal directory control layer error: Requested server name not found.
> I suspect this will be a hard question to answer but I'd appreciate any
> input.
>
> Cheers
> Dave
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server-connectivity/200801/1
>
|||Hi,
Thanks for your reply, I was using it last week, my PC burnt out and I
replaced it and used my old hard drive as a slave so I could have all my old
applications etc. I am using "Sybase System10" as my Driver? My knowledge
is quite limited in this area sorry if I am missing something silly here.
Regards
Dave
Rick Byham, (MSFT) wrote:[vbcol=seagreen]
>This is a pretty general error. It could be caused by your network, or by
>SQL Server settings. You didn't say how long ago it worked. Yesterday, or
>last year? If yesterday you may have changed something. If last year, it
>could be lots of things.
>You didn't say what version you are using. If SQL Server 2005, check out the
>connectivity tutorial which was designed to help users with just this
>problem. http://msdn2.microsoft.com/en-us/library/ms345318.aspx
>[quoted text clipped - 13 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-connectivity/200801/1
|||What version of SQL Server are trying to connect to?
Is SQL Server on the same computer or a different computer?
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Suttd via droptable.com" <u25367@.uwe> wrote in message
news:7e34deec0e23c@.uwe...

> Hi,
> Thanks for your reply, I was using it last week, my PC burnt out and I
> replaced it and used my old hard drive as a slave so I could have all my
> old
> applications etc. I am using "Sybase System10" as my Driver? My
> knowledge
> is quite limited in this area sorry if I am missing something silly here.
> Regards
> Dave
>
> Rick Byham, (MSFT) wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server-connectivity/200801/1
>

Connecting two cubes

I am using SSAS 2005 and I have a situation where I have two different cubes that I need to link up so that I can get related data from one cube to the other.

Here's the scenario:
I have a customer cube that gives me metrics about how many new customers, inactive customers, etc based on date ranges and other criteria. What I need to be able to do is once I have a subset of customers I want to be able to look at related measures that belong to a different cube. I have thought about making a large cube that contains multiple fact tables and allows me to grab both measures as necessary. The reason I'm trying to avoid this approach is because the customer data is going to be changing (a customer becomes inactive) and will require a full process on the customer cube. There are currently only about 100K customers, so the reprocess time is fairly minimal. The related data has several 100 million rows requiring a siginificant time to fully process. So, it isn't practical to have it all in the same cube where everything would have to be reprocessed. So, my questions are: Can I link two cubes together (sort of like virtual cubes in AS 2000) so that I can follow information across two cubes? Or if I did include a second fact table in the cube can I only process the fact table related to customer information and not the one containing the related data?

Thanks!

You should be able to create a 2nd measure group for the 2nd fact table in the original cube, but only process the 1st measure group:

http://msdn2.microsoft.com/en-us/library/ms175634.aspx

>>

...

Processing a Measure Group

When you process a measure group, Analysis Services processes some or all of the partitions within the measure group, and any unprocessed dimensions that participate in the measure group. Specifics of the processing job depend on the processing option that you select. You can process one or more measure groups in Analysis Services without affecting other measure groups in a cube.

Note:
You can process individual measure groups programmatically, or by using SQL Server Management Studio. You cannot process individual measure groups in Business Intelligence Development Studio unless you do so by partition. ... >>

Connecting to SQL Server via MS Access-Issue

We have a user who can connect via link tables to sql to one database oak.
On the other database (which he has exact same permissions) he gets timeout
message (ODBC Call Failed). He can oly see one table in link tables with th
e
database in question, the other he can see all of the tables. The user can
connect via Query Analyzer aok to both databases and see all the tables.
Could any shed some light on what maybe the issue and a workaround?
ThnxsIf it doesn't appear to be an issue with SQL Server, then look at
DSN's, or any other client-side settings which may be different.
--Mary
On Thu, 7 Sep 2006 08:29:02 -0700, PDavies
<PDavies@.discussions.microsoft.com> wrote:

>We have a user who can connect via link tables to sql to one database oak.
>On the other database (which he has exact same permissions) he gets timeout
>message (ODBC Call Failed). He can oly see one table in link tables with t
he
>database in question, the other he can see all of the tables. The user can
>connect via Query Analyzer aok to both databases and see all the tables.
>Could any shed some light on what maybe the issue and a workaround?
>Thnxs

Connecting to SQL Server via MS Access-Issue

We have a user who can connect via link tables to sql to one database oak.
On the other database (which he has exact same permissions) he gets timeout
message (ODBC Call Failed). He can oly see one table in link tables with the
database in question, the other he can see all of the tables. The user can
connect via Query Analyzer aok to both databases and see all the tables.
Could any shed some light on what maybe the issue and a workaround?
ThnxsIf it doesn't appear to be an issue with SQL Server, then look at
DSN's, or any other client-side settings which may be different.
--Mary
On Thu, 7 Sep 2006 08:29:02 -0700, PDavies
<PDavies@.discussions.microsoft.com> wrote:
>We have a user who can connect via link tables to sql to one database oak.
>On the other database (which he has exact same permissions) he gets timeout
>message (ODBC Call Failed). He can oly see one table in link tables with the
>database in question, the other he can see all of the tables. The user can
>connect via Query Analyzer aok to both databases and see all the tables.
>Could any shed some light on what maybe the issue and a workaround?
>Thnxs