once you ensure it is numeric either
ensure it is within a range ie
1950 -> 2050+
or
if len(cstr(iYear)) = 4 then
' Valid
end if
will ensure it is the correct year length (part 2 of your question)
The reason you get no recordset is InterDev although reading the DLL headers to offer up the intellisense while developing does not actually know what the option Values are as integers.
Adding the DLL as a reference to the ASP solution should sort that out, passing the integer value 1 I assume...
ok after re-reading it the first part (stored procedure change) is optional
change
select * from my_view
where BALANCE < 0
set @HowMany =@@RowCount
in the SP to
select @HowMany = Count(*)
from my_view
where BALANCE < 0
the ado code looks fine, except maybe specifying adParamInputOutput...
One point to consider is if the execute method behaves the same as transfer, ie
Server.transfer "PageB.asp?SomeParam=-1" Will fail because it has params specified
Server.transfer "PageB.asp" transfers to the next page correctly *and* hands the current QueryString onto...
even if you did connect to "\\b\wherever\script.vbs", and execute the file, it would still execute on cpu A, after dragging off the disk shared by B.
The only method I know of to get CPU B, to execute the script is to put waders on and get inside the windows internals, you'll need to...
I wish you could edit these :)
Session.Contents("outpostDB.StartsSecc") Request.form"p_name")
Should actually be
Session.Contents("outpostDB").StartsSecc Request.form("p_name")
d'oh
Session.Contents("outpostDB.StartsSecc") Request.form"p_name")
Should be (i think)
Session.Contents("outpostDB.StartsSecc") Request.form("p_name")
could you post the first 5 or 6 lines from the page ?
it should read
<%@ Language=VBScript %>
<% Option Explicit %>
<HTML>
<HEAD>
</HEAD>
<BODY>
</BODY>
</HTML>
etc
The language declaration needs to be in it's own line (along with transaction specifcation if needed)
try
<%@LANGUAGE="VBScript" %>
<% Option Explicit
' Insert other code where required
%>
The code you have posted runs at the server, and any button or onclick event would be running in the client browser.
your only way to complete this is to store outpostDB in a session variable
set Session.contents("outpostDB") = createObject("TAPI.CLSCONN")...
heh tried that already and on the local machine is fine and a little faster, on a remote machine the page stops loading for no reason, view source and the server spits out some little message about buffering must be on :(
Sigh
Thanks for all the suggestions so far.
Will certainly look into it however I believe the problem is the browser (ie 5.5sp2) rendering or at least allocating resources for the page. It pages up 80mb of memory but the html stream isn't that massive 338kb for the whole page.
I am going to look into the getrows method and also another...
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.