Problems with asp page

[dmkrishna]

Hi,
My asp page is giving an error "parameter in correct". Please help me to find and fix this.
Thanks,
Murali...

[Roy Sinclair]

"Parameter incorrect" is caused by an incorrect parameter. If you want more specific help you need to provide more specific information. I'm getting old so I can't peer a thousand miles to look at code over your shoulder, you need to post something relevant here so I only have to look the few feet between my head and my own monitor.

[dmkrishna]

Hi Sinclair,
Thank you for your reply. I'll check all the sql queries in my code. If i'm unable to fix this I'll come to you.
Thanks,
Murali...

[whammy]

Does it give you a line number?

Usually the best thing to do if it's a SQL statement throwing the error is to response.write the whole thing to the page.

[dmkrishna]

Hi Whammy,
Here is the situation. The page is working fine with our team and most of our customers. But Recently we got a potential customer. He tried to place some orders using the site from his laptop while he is in a tour. He got this error "parameter incorrect". I'm unable to reproduce the same error. Because i used the latest browsers. So i'm checking the site in older versions of netscape. Earlier i tested this site on a couple of other browsers (Opera, Netscape7.0, ie5, ie5.5, ie 6). But i got problem when i tried to open the site in netscape4.05. So need to do some QA on this code. There we used some vbscript, javascript and database connection using ado.
Thanks,
Murali...

[Roy Sinclair]

If you have access to the server logs and any clue about when the user tried to access your site see if you can find when the potential customer tried to get in. The log file probably has the browser version the user tried with so you can narrow down the possibilities more quickly. The log files may also give you additional answers about what the potential customer was trying to do.

[whammy]

Hey... by any chance is the page in question transferrring values in the querystring using javascript? I got that same EXACT error once testing with NS 4.78. I think perhaps:

escape()

in javascript might need to be used to fix the querystring! But I haven't tested this yet.