Re: data acces page connect to sql server

Tech-Archive recommends: Fix windows errors by optimizing your registry



and for the record, moving to ASP.net is not reccomended, because it
runs slower and it complicates things on the clientside without any
real benefit










On Dec 31 2008, 1:48 pm, "Sylvain Lafontaine" <sylvain aei ca (fill
the blanks, no spam please)> wrote:
These parameters look OK.  However, a lot of potential problems could block
the connection even if the parameters are OK; like a firewall for example..

The first thing to check would be to remove any blank space after each « ; »
(don't remember if it's important or not); the second would be to specify
the protocol to be used as well as the port (often but not necessarily 14330
by adding the name of the library (network) or one of the prefix tcp: or np:
; for example:

ODBC:
Driver={SQL Server}; Server=jack8.db.2965895.hostedresource.com;
Database=jack8; Uid=jack8; Pwd='your password';Network=DBMSSOCN

ODBC:
Driver={SQL Server}; Server=jack8.db.2965895.hostedresource.com,1433;
Database=jack8; Uid=jack8; Pwd='your password';Network=DBMSSOCN

OLE DB, OleDbConnection (.NET):
Provider=sqloledb; Data Source=tcp:jack8.db.2965895.hostedresource.com;
Initial
Catalog=jack8; User ID=jack8; Password='your password';

OLE DB, OleDbConnection (.NET):
Provider=sqloledb; Data Source=tcp:jack8.db.2965895.hostedresource.com,1433;
Initial
Catalog=jack8; User ID=jack8; Password='your password';

Using an Alias (see SQL-Server Client Network Utility or something like
that, depends of the version of SQL-Server used on your local machine) will
often solve some of these connection problems.  A fourth thing to try would
be to connect using another program such as Enterprise Manager or SQL-Server
Management Studio to see if there is anything wrong with the setup of your
Data Access Page.  You also don't say if you're able to connection to any
other SQL-Server like an instance on your local machine.  Trying to ping the
address could also be a good idea.

If the SQL-Server is not the default instance but a named instance, then you
must add the name of the instance after the address of the server (but
before the port number).  However, as these parameters have been given to
you; I don't think that's your problem here.  Finally, you can take a look
at the following articles to help you troubleshooting connection problem:

http://www.datamasker.com/SSE2005_NetworkCfg.htm

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx

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





"JACK88" <u48513@uwe> wrote in messagenews:8f76b1da08e35@xxxxxx
Hi, i cannot figure out the address host name when i want to connect my
data
acces page to the microsoft OLE DB PROvider for sql server so that i can
link
(in data link properties) my data access page to the  sql server. The
following address I was given are

ODBC:
Driver={SQL Server}; Server=jack8.db.2965895.hostedresource.com;
Database=jack8; Uid=jack8; Pwd='your password';

OLE DB, OleDbConnection (.NET):
Provider=sqloledb; Data Source=jack8.db.2965895.hostedresource.com;
Initial
Catalog=jack8; User ID=jack8; Password='your password';

SqlConnection (.NET):
Data Source=jack8.db.2965895.hostedresource.com; Initial Catalog=jack8;
User
ID=jack8; Password='your password';

Thxs.

Confused: Is this the right way to display my drop down combo box in the
data
access page by linking the data access page to sql server? Or is there
more
correct way?

The correct way is not to use Data Access Pages anymore.  This technology is
practically dead and is a lost of time.  While there are more or less easy
to start up with at the beginning; later, they become practically impossible
to use/develop when you want to do anything more advanced than a simple
basic form.  Believe me, I know from personal experience.  They're also
subject to the main problem of modern security: they're usually blocked by
any intervening firewall and deblocking the firewall to let them go
through - when you have the permission to do so - is puncturing a big hole
into it.

In my opinion, you should stop trying to use this old stuff and switch to
something like ASP.NET.

Thxs. Jack

Happy New Year 2009!

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)- Hide quoted text -

- Show quoted text -

.



Relevant Pages

  • Re: data acces page connect to sql server
    ... I believe that we should all stand in unison, _BEGGING_ Microsoft to ... Using an Alias (see SQL-Server Client Network Utility or something like ... acces page to the microsoft OLE DB PROvider for sql server so that i can ... my data access page to the  sql server. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: data acces page connect to sql server
    ... switching to ASP.NET is not an easy thing and there are a lot of things ... SQL-Express and SQL-Server 2008, the VWD is the free version of its bigger ... often solve some of these connection problems. ... The correct way is not to use Data Access Pages anymore. ...
    (microsoft.public.access.adp.sqlserver)
  • Deploying Access Data Pages
    ... I am connecting to a SQL Server database with a Data ... While deploying the data access page in other machines, ...
    (microsoft.public.sqlserver.security)
  • Re: data acces page connect to sql server
    ... the connection even if the parameters are OK; like a firewall for example. ... Using an Alias (see SQL-Server Client Network Utility or something like ... my data access page to the sql server. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Binding Access Forms to a SQL Server Data source : View Or Sto
    ... Goldmine on SQL with 12 users. ... On the same SQL Server, ... It still uses BDE for data access. ... My form source is a Stored Procedure that returns ...
    (microsoft.public.access.adp.sqlserver)