Access 2003 / SQL Server 2005 linking.

I have an Access 2003 database that I have split, then upsized to SQL Server
2005. The database works find on the machine that has the SQL Server 2005,
but when I try to run the program from another machine on the network, I get
the following error:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
Now I have done everything suggested by Microsoft's documentation
(http://support.microsoft.com/default.aspx/kb/914277), including setting the
SQL Server Surface Area Configuration tool and modifying the firewall
settings.
Does anyone have any other suggestions I can try?
(I think the problem may be in my dsn file, but I am not sure.)
Larry J. West, MCSD, MOUS, FLMI, ACS
Same error I was getting.
My problem was caused by an alias set up in client network utility to the
server.
I just deleted the alias and then Access connected fine.
Gary
"LarryWestMCSD" wrote:

> I have an Access 2003 database that I have split, then upsized to SQL Server
> 2005. The database works find on the machine that has the SQL Server 2005,
> but when I try to run the program from another machine on the network, I get
> the following error:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> Now I have done everything suggested by Microsoft's documentation
> (http://support.microsoft.com/default.aspx/kb/914277), including setting the
> SQL Server Surface Area Configuration tool and modifying the firewall
> settings.
> Does anyone have any other suggestions I can try?
> (I think the problem may be in my dsn file, but I am not sure.)
> --
> Larry J. West, MCSD, MOUS, FLMI, ACS

Access 2003 / SQL Server 2005 linking.

I have an Access 2003 database that I have split, then upsized to SQL Server
2005. The database works find on the machine that has the SQL Server 2005,
but when I try to run the program from another machine on the network, I get
the following error:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
Now I have done everything suggested by Microsoft's documentation
(http://support.microsoft.com/default.aspx/kb/914277), including setting the
SQL Server Surface Area Configuration tool and modifying the firewall
settings.
Does anyone have any other suggestions I can try?
(I think the problem may be in my dsn file, but I am not sure.)
--
Larry J. West, MCSD, MOUS, FLMI, ACSSame error I was getting.
My problem was caused by an alias set up in client network utility to the
server.
I just deleted the alias and then Access connected fine.
Gary
"LarryWestMCSD" wrote:

> I have an Access 2003 database that I have split, then upsized to SQL Serv
er
> 2005. The database works find on the machine that has the SQL Server 2005
,
> but when I try to run the program from another machine on the network, I g
et
> the following error:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> Now I have done everything suggested by Microsoft's documentation
> (http://support.microsoft.com/default.aspx/kb/914277), including setting t
he
> SQL Server Surface Area Configuration tool and modifying the firewall
> settings.
> Does anyone have any other suggestions I can try?
> (I think the problem may be in my dsn file, but I am not sure.)
> --
> Larry J. West, MCSD, MOUS, FLMI, ACS

Access / SQL Server currency datatypes

When linking a SQL server 2000 table to Access 2003 using the standard MS
ODBC driver (2000.85.1117.00) fields with a datatype money and smallmoney
are blank in Access.
If I use a DataDirect ODBC driver the money fields are displayed correctly.
Any Idea if there is a MS ODBC driver that displays money correctly?
You might want to ask this question in one of the Access newsgroups
since it isn't an ODBC or a SQL Server issue. Someone there may have
the answer you seek.
--Mary
On Tue, 14 Mar 2006 06:02:26 -0600, "Simon
Lampert"<ureader@.byteaccess.com> wrote:

>When linking a SQL server 2000 table to Access 2003 using the standard MS
>ODBC driver (2000.85.1117.00) fields with a datatype money and smallmoney
>are blank in Access.
>If I use a DataDirect ODBC driver the money fields are displayed correctly.
>Any Idea if there is a MS ODBC driver that displays money correctly?

Access / SQL Server currency datatypes

When linking a SQL server 2000 table to Access 2003 using the standard MS
ODBC driver (2000.85.1117.00) fields with a datatype money and smallmoney
are blank in Access.
If I use a DataDirect ODBC driver the money fields are displayed correctly.
Any Idea if there is a MS ODBC driver that displays money correctly?You might want to ask this question in one of the Access newsgroups
since it isn't an ODBC or a SQL Server issue. Someone there may have
the answer you seek.
--Mary
On Tue, 14 Mar 2006 06:02:26 -0600, "Simon
Lampert"<ureader@.byteaccess.com> wrote:

>When linking a SQL server 2000 table to Access 2003 using the standard MS
>ODBC driver (2000.85.1117.00) fields with a datatype money and smallmoney
>are blank in Access.
>If I use a DataDirect ODBC driver the money fields are displayed correctly.
>Any Idea if there is a MS ODBC driver that displays money correctly?