If you're testing the value of a variable you need to use the '=' twice. So your first line would need to be:
if(document.step3[FieldName].value == ''.
A single '=' is only used when assigning a value to a variable.
The path to freedom is seldom trodden by the multitude.
You could try using the IsNull() function.
E.g. Select IsNUll(expr1,0)+ IsNull(expr2,0)
If either expr1 or expr2 is null the function will return 0 (or any other value you want to use as the second parameter for the function).
The path to freedom is seldom trodden by the multitude.
As far as I know 2147217887(80040e21) is a general code for ODBC errors - so the problem may be down to data access rather than a configuration management issue specific to Windows XP.
The path to freedom is seldom trodden by the multitude.
Hi there
Check whether the Sql Server service is running under the 'LocalSystem' account - if it is then it won't be able to access the network.
The path to freedom is seldom trodden by the multitude.
Hi There
the only way I can think of doing this is to use the VB Extensibility library. I think you can reference a collection of forms in a VB project by using the VB components class of the VBIDE library.
You might find this helpful...
Hi there
I know you've mentioned that you've tried running this in a number of different ways,but here are a couple of comments:
i) I think that the length of @LocID should be defined as 4 rather than 15,i.e. it's a 32 bit integer.
ii) You are creating the @LocationName parameter but do not...
Try checking the length of the values you are using to populate the Command Object parameters. This error can occur if they are longer than the length specified in the Stored Procedure definition itself.
I myself have been caught out by this problem in the past when a particularly long email...
Mr3Putt is right that the main issue is dealing with apostrophes. Although the method of dealing with this is not to replace apostrophes with an empty string but to double them up like so:
Replace(username,"'","''")
However, this is not merely a syntactical issue. By...
It seems to be a problem in the logic of your procedure. If no username is passed through then you do not generate any sql. However, you are still continuing with the procedure and executing an empty sql string - hence the error.
It might also be worth pointing out that, from a security point...
Hi There
Try using this sql statement after the truncate:
DBCC CHECKIDENT(TableName, RESEED, 0)
The path to freedom is seldom trodden by the multitude.
Hi There
Your code should look something like this:
<td ALIGN="left" valign="top"><a href="ViewAuthor.asp?AuthorID=<%=rs("AuthorID")%>"><%=rs("Author")%></a></td>
The href attribute needs to be the name of the page you want to link to.
The...
Hi There
The following Javascript should work in Internet Explorer (version 4 or above) for adding the current page to the user's favourites.
Obviously you can alter the parameters to suit your needs.
window.external.AddFavorite(location.href, document.title).
It's a bit surprising since, as I understand it, Microsoft used to recommend using underscores at one stage.
Hopefully you'll find this URL helpful:
http://www.iisfaq.com/default.aspx?View=A508&P=1
Have you instantiated the recordset object? You need to do this:
Dim RS
Set RS=Server.CreateObject("ADODB.Recordset")
If this still fails make sure that you have successfully installed ADO on the server.
I experienced a similar problem when our users upgraded to IE6. The cause turned out to be that the server name contained an underscore and IE6 no longer persists asp sessions on servers whose name contains the underscore character.
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.