You need to check the data type of the 2 variable to see if they are the same, using VarType(rs2("hakemnot")) If the value is 8 then it is a string, you need to convert it.
Here is the link to check the data type of a variable:
http://www.w3schools.com/vbScript/func_vartype.asp
Set con = Server.CreateObject("ADODB.Connection")
con.ConnectionTimeout = 10
con.cursorlocation=3
Set cmd = CreateObject("ADODB.Command")
cmd.CommandTimeout = 10
This didn't work either. Does anyone know why??? thanks.
ASP, IIS6
Set con = Server.CreateObject("ADODB.Connection")
con.ConnectionTimeout = 10
con.CommandTimeout = 10
con.cursorlocation=3
strConnection = "DSN=blab ...;uid=...;pwd=...."
con.Open strConnection
These timeout setting don't work. My query run for 15 seconds and it's not time out. How...
No, it's not the permission issue. I'm switching from EDBC to ODBC driver using the same DB. Didn't have any problem with EDBC.
P.S. It's good to see you are still in this forum. It's been a long time.
I'm trying to insert a record to a db and I got this error.
Set con = Server.CreateObject("ADODB.Connection")
con.Open "DSN=MyDB;uid=myuid;pwd=mypwd"
con.Execute("insert into myTable values (...,...,blab,blab)")
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[CA][ODBC...
I'm trying to set up some restriction on a web page. I have this piece of code:
<%
if time() >= CDate("8:00:00 AM") and time() <= CDate("5:00:00 PM")
.... blab ..blab ...
end if %>
I tested it on the server, it works as expected. But for some unknown reasons, this setting doesn't work for...
Make sure that you have admin privilege on the server.
If you do have admin privilege, then probably it is a security with IIS. What version of IIS do you have? You might need to update to IIS 7.0
I found this link shows how to create drop down list using vbscript, I hope it will help.
http://computer-programming-tutorials.suite101.com/article.cfm/how_to_create_dynamic_comboboxes_with_vbscript
There you go.
Another solution is to post the form back using the form action:
On page1.asp
<form name="form1" method="post" action="page1.asp">
Then you check to see if the form is posted back, this piece of code will only execute when the form is posted back.
<%
If...
Well, I would break that hundred lines of code further. Put the rest of the execution in a sub. When you popup a new window, do some stuffs, then you close it. On unload event of this popup window, execute the rest of the execution by calling that sub.
The page that displays the message is popup window? If it is a popup window, you will need some javascript to refresh parent window. If it is not, like I said, after user click update button, instead of going to the page to display the message, go back to the "textarea" page. This "textarea"...
Ah, I think I know what you want. Instead of taking the user to the update page, just take them back to the display page. If you want to inform user that the record has been updated, you can display a message on the page or popup a window to say so.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.