Office 2003 Web Service Reference Tool fails on ReportingService

I am trying to add a web reference to an Access 2003 database form using the
latest version of the Web Services Toolkit. When I try to add the reference
it runs for a while and then blows up with the following message.
Cannot Create Class.
The Web Service References Tool could not generate the requested code. Any
changes that were made to your project have been rolled back.
Any help would be appreciated.this newsgroup is for SQL Server Reporting Services. You will get better
responses if you post this in one of the Access newsgroups.
"TMesich" <TMesich@.discussions.microsoft.com> wrote in message
news:6EB2929F-C179-4348-B931-E15451985189@.microsoft.com...
>I am trying to add a web reference to an Access 2003 database form using
>the
> latest version of the Web Services Toolkit. When I try to add the
> reference
> it runs for a while and then blows up with the following message.
> Cannot Create Class.
> The Web Service References Tool could not generate the requested code.
> Any
> changes that were made to your project have been rolled back.
> Any help would be appreciated.

ODBC to SQL Server through DSN fails once in a while

Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.odbc:43808
Hello:
I have multiple ODBC connections to our SQL Server, and they are mostly
working well.
I have an issue once in a while with the connection when the DSN is not the
DSN used to create the linked table. For example, If the DSN is named the
same, but is connecting through IP address vs. Computer Name, the connection
will fail.
I just thought I'd post this to see if there are other similar situations,
maybe some ways around it?
Thanks,
Kyle
"Kyle McAdam" <kyle.mcadam@.sympatico.ca> wrote in message
news:Tw%dd.56921$JG5.927915@.news20.bellglobal.com. ..
> Hello:
> I have multiple ODBC connections to our SQL Server, and they are mostly
> working well.
> I have an issue once in a while with the connection when the DSN is not
the
> DSN used to create the linked table. For example, If the DSN is named the
> same, but is connecting through IP address vs. Computer Name, the
connection
> will fail.
> I just thought I'd post this to see if there are other similar situations,
> maybe some ways around it?
> Thanks,
> Kyle
In the DSN configuration, click Client Configuration and make sure TCP/IP is
checked as a protocol. You can also Alias a server name in this screen. I've
found that to work well.

ODBC to SQL Server through DSN fails once in a while

Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.odbc:43808
Hello:
I have multiple ODBC connections to our SQL Server, and they are mostly
working well.
I have an issue once in a while with the connection when the DSN is not the
DSN used to create the linked table. For example, If the DSN is named the
same, but is connecting through IP address vs. Computer Name, the connection
will fail.
I just thought I'd post this to see if there are other similar situations,
maybe some ways around it?
Thanks,
Kyle"Kyle McAdam" <kyle.mcadam@.sympatico.ca> wrote in message
news:Tw%dd.56921$JG5.927915@.news20.bellglobal.com...
> Hello:
> I have multiple ODBC connections to our SQL Server, and they are mostly
> working well.
> I have an issue once in a while with the connection when the DSN is not
the
> DSN used to create the linked table. For example, If the DSN is named the
> same, but is connecting through IP address vs. Computer Name, the
connection
> will fail.
> I just thought I'd post this to see if there are other similar situations,
> maybe some ways around it?
> Thanks,
> Kyle
In the DSN configuration, click Client Configuration and make sure TCP/IP is
checked as a protocol. You can also Alias a server name in this screen. I've
found that to work well.