«

Big Moxy wrote:
> On Nov 29, 5:10 pm, "Bob Barrows [MVP]" <reb01...@NOyahoo.SPAMcom>
> wrote:
>> Big Moxy wrote:
>>
>>> I placed it where I did because the initial page display uses sql =
>>> "SELECT * FROM [" & tables(tableID) & "] ORDER BY ID ASC" which
>>> works just fine. I will never get the search option if the
>>> Response.End is placed where you suggest.
>>
>> I don't get you. if you want to troubleshoot the sql statement, then
>> you have to print it out before it is executed ...
>> --
>> Microsoft MVP - ASP/ASP.NET
>> Please reply to the newsgroup. This email account is my spam trap so
>> I don't check it very often. If you must reply off-line, then remove
>> the "NO SPAM"
>
> Perhaps you are not understanding the sequence of events.

It's irrelevant. Your goal at this point is not to make the page run to
completion. Your goal at this point is to discover what the sql string
contains (at least, that was the goal you stated in your opening post).
Nothing else that happens after the sql string is built is relevant until
you determine that your sql statement is correct. Once you have determined
that the sql statement is what you expect it to be, then you can start
worrying about getting the rest of the page to run.

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Big Moxy wrote:

> So as you can see if I place the Response.End after the End If and
> before the Open I will never get a display.

Oh damn - my previous repoly was *******s.
I need to look at this again tomorrow

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Big Moxy wrote:
> NEVER MIND. I WILL SIMPLY SPLIT THE PAGES AND TROUBLESHOOT THE SEARCH
> RESULTS SEPARATELY.

Oh shoot - you got to this too quick. You're right - my previous reply was
crap - I need to shut the computer off ... now.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Just a thought
Why not use "On Error" to control the Response.Write and Response.End

ByTheWay, you used "Response.End()" - I dont us the brackets for this
statement

Pete (Northolt UK)

Big Moxy wrote:

> I'm getting this error on my asp/access page. It's a sql error
> triggered by Recordset1.open sql,conn,1,1. The sql is constructed from
> user input on a search page.
>
> ADODB.Recordset error '800a0bb9'
> Arguments are of the wrong type, are out of acceptable range, or are
> in conflict with one another.
>
> The problem I'm having is getting a Response.Write(sql) to actually
> display the sql code before the open statement.
>
> Can someone please help me display my generated sql code?
>
> Thank you!

Big Moxy wrote:

>
> NEVER MIND. I WILL SIMPLY SPLIT THE PAGES AND TROUBLESHOOT THE SEARCH
> RESULTS SEPARATELY.

Sorry about yesterday. Are you still here? Do you still need help with
this?

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.