Re: Stored Procedure from Access

i don't want it to prompt for credentials. i just have never used a
connection string within access to access a particular sql server.

Below is some sample asp code that runs a SPROC. I'm just trying to do
something just like this, except from within access.

What would a proper access to sql connection string look like?

ASP CODE ******************

sDSN = "Provider=SQLOLEDB.1;Persist Security Info=True;User
ID=user;Password=pwd;Initial Catalog=myDatabase;Data
Source=192.168.1.999;Use Procedure for Prepare=1;Auto Translate=True;Packet
Size=4096;"

Set objConn = CreateObject("ADODB.Connection")
objConn.Open sDSN

Set objRS = Server.CreateObject("ADODB.Recordset")

sSQL2 = "MY_SPROC"
objRS.Open sSQL2, objConn



"Dirk Goldgar" <dg@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23Rz3tEqYGHA.3516@xxxxxxxxxxxxxxxxxxxxxxx
"scott" <sbailey@xxxxxxxxxxxxxxx> wrote in message
news:%23$xf26pYGHA.3704@xxxxxxxxxxxxxxxxxxxx
My problem is that i'm linking to the sql tables.

I don't follow you. When you use a pass-through query or execute a
stored procedure via an ADO connection to the server, it doesn't involve
linked tables at all. You have to specify a suitable connect string for
the query, of course, and for the ADO method you have to provide a
Connection object, which will have to be opened with a suitable connect
string.

can your code be
modified so a server and login credentials be supplied?

I'm not sure what you have in mind. I usually use Windows
Authentication for the SQL Server connection, but if you're not going to
do that, I believe you can pass the credentials as part of the connect
string. Are you talking about having your code prompt the user for the
connect string and credentials, and then building the connect string on
the fly?

can i use the same asp code i use within access to run a sproc?

I don't know what you mean. If you're talking about VBScript code from
an ASP application, then the ADO elements will be the same, though you'd
have to change calls to Server.CreateObject to just CreateObject (for
late binding).

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)




.

Relevant Pages

  • Re: Cannot Generate SSPI Context - help
    ... I have used the following DSN-less string: ... Microsoft OLE DB Provider for SQL Server error '80004005' ... When a connection is "trusted," it means ... > How would one connect to a remote SQL Server using Windows authen? ...
    (microsoft.public.inetserver.asp.db)
  • Re: Accessing an SQL Server database file
    ... Do you mind explaining to me how the connection string written their works? ... All systems have SQL Server Express and SQL Server 2005 installed. ... owningObject, SqlConnectionString connectionOptions, String newPassword, ...
    (microsoft.public.dotnet.languages.csharp)
  • RE: ASP.NET 2.0 deployment (w/ SQL Srvr 2005) error
    ... The connection string was ok. ... than the SQL Server Instance, ... owningObject, SqlConnectionString connectionOptions, String ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Custom membership provider problem
    ... SQL server 2005 does not install with the TCP/IP protocol turned on. ... >An error has occurred while establishing a connection to the server. ... 25 - Connection string is not valid) ... >Boolean& failoverDemandDone, String host, String failoverPartner, String ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: ASP .Net connection to Sql Server
    ... Using "dbmssocn" tells it to use the TCP/IP network driver, ... It is connecting via a connection string similiar to: ... > string to our production SQL server and everything runs fine. ...
    (microsoft.public.dotnet.framework.aspnet)