Problem getting external data using Access

Hello.
I would appreciate any assistance in finding a solution to this problem.
I am using an access program that connects to an access database. The
program was written using Access 2000. However, the program does not properly
connect to the database, depending on the computer on which it is installed,
or the operating system of the computer on which the program has been
installed.
For example, the connection fails on any computer that uses Windows 98. It
works for the most part on computers using Windows 2000, any version, but it
failed to connect properly on a Toshiba laptop computer that had Windows 2000.
The program opens properly, but the data that should appear from the
database cannot be accessed. The database records are hidden by the program,
and can be viewed when the database is unhidden. Nonetheless, the records
cannot be manipulated by the program.
Thank you very much in advance for your time and suggestions.
Regards,
The Seefahrer
If you have Access program installed on the computer, then use it to
determine if there are any problems with opening the .mdb file that you
want to access. Check for error messages as they provide insight into what
the problem could be.
James
***Disclaimer: This posting is provided "as is" with no warranties and
confers no rights.***
--
>Thread-Topic: Problem getting external data using Access
>thread-index: AcTmMQytVaJhB1ULSXmwYuabzWov8w==
>X-WBNR-Posting-Host: 4.159.163.153
>From: =?Utf-8?B?U2VlZmFocmVy?= <Seefahrer@.discussions.microsoft.com>
>Subject: Problem getting external data using Access
>Date: Sun, 19 Dec 2004 17:13:01 -0800
>Lines: 24
>Message-ID: <C5C0E0CF-3D41-4692-9AE8-623A3A761827@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.connect
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.connect:44010
>X-Tomcat-NG: microsoft.public.sqlserver.connect
>Hello.
>I would appreciate any assistance in finding a solution to this problem.
>I am using an access program that connects to an access database. The
>program was written using Access 2000. However, the program does not
properly
>connect to the database, depending on the computer on which it is
installed,
>or the operating system of the computer on which the program has been
>installed.
>For example, the connection fails on any computer that uses Windows 98. It
>works for the most part on computers using Windows 2000, any version, but
it
>failed to connect properly on a Toshiba laptop computer that had Windows
2000.
>The program opens properly, but the data that should appear from the
>database cannot be accessed. The database records are hidden by the
program,
>and can be viewed when the database is unhidden. Nonetheless, the records
>cannot be manipulated by the program.
>Thank you very much in advance for your time and suggestions.
>--
>Regards,
>The Seefahrer
>

Problem connection to SQL Server with ODBC

Hi,
Getting very frustrated by the following problem, using SQL Server 2000 (inc
SP3a), using an application that connects to a DB via ODBC and the following
error message comes up:
Connection failed:
SQLSTATE: '01000'
SQL Server Error: 1703
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error:17
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server doe
s not exist
or access denied
When setting up the DSN the test works fine as does query analyzer, pretty
sure it's not the application I'm using as the SQL server connection window
that comes up after the initial error (above) gives the same error message.
Any ideas? Help is definitely needed before I tear my hair out!
Thanks
IanWhat protocols are being used by the client and what is the
server listening on?
Are the client network utilities on the clients having the
connectivity problems?
Are you using an alias for the connection?
What version of MDAC on the clients?
From your description, it sounds like the app tries to
connect twice (which is fine) but that it's just not hitting
the right protocols. You can find information on how a
client runs through the protocols trying to connect in this
article:
INF: SQL Server Clients May Change Protocols When They Try
to Connect
http://support.microsoft.com/?id=328383
You can also find some general troubleshooting for the error
at:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306
-Sue
On Tue, 6 Apr 2004 10:12:37 +0100, "Ian Spanswick"
<ian.spanswick@.eps-hq.co.uk> wrote:

>Hi,
>Getting very frustrated by the following problem, using SQL Server 2000 (in
c
>SP3a), using an application that connects to a DB via ODBC and the followin
g
>error message comes up:
>Connection failed:
>SQLSTATE: '01000'
>SQL Server Error: 1703
>[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpe
n
>(Connect()).
>Connection failed:
>SQLState: '08001'
>SQL Server Error:17
>[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server do
es not exist
>or access denied
>When setting up the DSN the test works fine as does query analyzer, pretty
>sure it's not the application I'm using as the SQL server connection window
>that comes up after the initial error (above) gives the same error message.
>Any ideas? Help is definitely needed before I tear my hair out!
>Thanks
>Ian
>|||Thanks for the links, studying them now but have moved my database to
another server and things are going better! Still want to get to the bottom
of the problem.
Ian
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:i3i670lutthh68l5mqlgn479ng66ornom3@.
4ax.com...
> What protocols are being used by the client and what is the
> server listening on?
> Are the client network utilities on the clients having the
> connectivity problems?
> Are you using an alias for the connection?
> What version of MDAC on the clients?
> From your description, it sounds like the app tries to
> connect twice (which is fine) but that it's just not hitting
> the right protocols. You can find information on how a
> client runs through the protocols trying to connect in this
> article:
> INF: SQL Server Clients May Change Protocols When They Try
> to Connect
> http://support.microsoft.com/?id=328383
> You can also find some general troubleshooting for the error
> at:
> INF: Potential Causes of the "SQL Server Does Not Exist or
> Access Denied" Error Message
> http://support.microsoft.com/?id=328306
> -Sue
> On Tue, 6 Apr 2004 10:12:37 +0100, "Ian Spanswick"
> <ian.spanswick@.eps-hq.co.uk> wrote:
>
(inc
following
exist
pretty
window
message.
>