I have a some code:
Rs.Open "[TableName]", Conn, 1,3,2
RS.AddNew
RS.Fields("Account_Name").Value = request.Form("Account_Name")
my question is does conn, 1,3,2 only write to the database not making the data readable? if i change it to conn, 0,1 i get page can't be displayed. I'm using access DB, with conn 1,3,2 it inserts fine, but when i go to query it i get no records found, but i see the data in the database, anybody have any ideas?
<%
Set Conn = Server.CreateObject("ADODB.Connection")
Conn.open application("dtat_motor_connectionstring")
set rs = new adodb.recordset
'Set RS = Conn.Execute(' "exec spcn_update_transactions &
customer_number, customer_name, customer_address, customer_city,
customer_state, customer_zip, customer_phone, vin,
acct_number, tag, title_number, tag_type_number, branch_number,
institution_number, yr_make, state_from, type_number)
response.write rs
%>
I'm I connecting them correctly. Is there and easier way to execute a stored procedure. I'm trying to insert data into a SQL page. I have to have the customer number returned to me asap for the next page.
I use this code all the time, but what does the ",,129" mean? Are there other parameters that one might use (I only do fairly simple SQL commands).
conn.execute strSQL,,129
Is there any way to modify the locktype when updating a database via a connection object's execute method? I have a game which worked completely fine when only ten or so people were playing, but as it grew into the hundreds, many people started getting errors and I'm 99% sure that they occur when the database tries to update when it's locked, which means that my connection execute statements are defaulting to pessimistic locking, which I don't want them to. Does anyone know how I can fix this?
View Replies View Relatedwhat is the best way to protect the connection strings keeping an effective, low overheaded access to them ?
I have a problem utilising my connection string to open more than one recordset in one ASP page.
The following code runs absolutley fine on a server running ASP 3, but falls over when run on a server running ASP 2 (the error says:
Microsoft JET Database Engine error '80004005'
Could not use ''; file already in use.
The code I am trying to run is: Code:
I searched the forum but I am still a little confused regarding the global.asa file. I created a global.asa file and it is in the root of the virdual directory. I then created a sub to initially connect to a datase such as: Code:
View Replies View RelatedI have 3 db connections, 2 of which are dsnless connections to access db's. Any of my previous existing pages that have recordsets from these db's work fine. I can add a new recordset to them and it works fine as well.
If I create a new page and add the same recordset in the same directory, I get the error msg saying something like "unable to open registry key" which from my understanding, means the page cant find the db.
Now I am using Dreamweaver 2004, and using their way to create connections where it creates a file, and then just adds an include statement an asp page if you use that connection.
Any good way to test this connection on the page or any ideas on how to troubleshoot where the path its pointing to is incorrect...im pretty much stuck at this point.
What is the best way to control is a transaction? I've done a little test and both of the examples below seem to do the job, but I was wondering which is the better method, this:
If err.number <> 0 Then
conn.RollbackTrans
Else
conn.CommitTrans
End If
Or this:
If conn.Errors.Count <> 0 Then
conn.RollbackTrans
Else
conn.CommitTrans
End If
I'm trying to access an access database by including the DB's password within the connection string. I try to connect to the DB, but I get and "Incorrect Password" error. What am I doing wrong?
set conn=Server.CreateObject("ADODB.Connection")
conn.Provider="Microsoft.Jet.OLEDB.4.0"; uid=admin; pwd="pass"
conn.Open(Server.Mappath("maindb.mdb"))
set rsUpdateEntry = Server.CreateObject("ADODB.recordset")
I am currently working on a small asp application. Now I would like to store the complete database connection in the application object. Note I want to store the connection NOT the connectionstring. For that purpose I wrote a small asp include which connects to the dbase and stores the connection object to the application object. However when I use this include in my pages then it doesnt work. What I am doing wrong? Here is the code:
View Replies View RelatedI recently installed IIS lockdown, and ever since my ASP pages have been hell. One problem is that now after a user views my ASP page which reads my local Access DB, the temporary file, .ldb, stays in the folder forever!
This temp file is created when a user opens the file, so I checked out the .ldb file and it says the ADMINISTRATOR is opening the file! How can the internet user be using the ADMIN account?! This is not good news! I will share my code for my page; however I have a feeling the code isn't the problem, but a setting is. Code:
Error info is as follows:
HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services
Technical Information (for support personnel)
Error Type:
error '8002801c'
Error accessing the OLE registry.
/iisHelp/common/500-100.asp, line 154
Is ADO a separate install? And from where?