Where is HTTPODBC.DLL discussed/supported

I'm shocked that there is so little discussion and suport of it out here. I
find the HTTPODBC.DLL very fast and very simple to setup, understand and
deploy. Granted, the world is moving towards ASP pages and away from
HTTPODBC but its still a very valuable and useful tool.

That being said - I did manage to find one single lone person in the entire
world having the same problem as me and it turns out that the HTTPODBC.DLL
was changed a few times in the last few months. It turns out that only one
version of the DLL seems to still work "properly" if you can call it that.
It works in that it doesn't limit text passing through it for GETS and
POSTS.

The PROPERLY functioning HTTPODBC.DLL that doesn't limit the amount of text
in a POST or a GET artificially came with


Granger Godbold has a great explanation of the verioning problem, and the
Cumulative Patch for IIS from article 811114 that actually contains the
"good" version of the DLL which is 5.0.2195.5663. The version after that
had more problems. <a style='text-decoration: underline;' href="http://dbforums.com/t857746.html" target="_blank">http://dbforums.com/t857746.html</a> His article actually
resolved my problem with the long text fields.

However I found 2 quirks with HTTPODBC.DLL now that its as it is:
1. It doesn't validate the RequiredParameters or check the DefaultParameters
in the IDC file and
2. If you put 2 dashes together without a space, in a field like this:

--

it will give an error when trying to pass thru the DLL "The system area for
this data call is too small" or similar.

----Mark Hripko






"Tim Coffey" <timcof DeleteThis @online.microsoft.com> wrote in message
news:T4t6UjBfDHA.536@cpmsftngxa07.phx.gbl...
 > This is it, however it is hard to find info, as very few people still use
it. The reason is people have moved to ASP, and even ASP.NET,
 > for much better performance reasons.
 >
 > I will bet you have gone to sp4, or the latest IIS rollup, and now this
doesn't work? Correct, it doesn't. They are currently bouncing
 > around some issues about re-enabling the functionality, but I believe
there was a security vulnerability exposed within the component,
 > thus the reason for this behavior.
 >
 > I would encourage you to move to ASP if possible, and give it a try
returning data. You will see a vast performance improvement,
 > especially if you are returning large amounts of data.
 >
 > Thank you. I hope this information is helpful.
 >
 > Tim Coffey [MSFT]
 >
 > This posting is provided "AS IS" with no warranties, and confers no
rights. You assume all risk for your use. © 2001 Microsoft
 > Corporation. All rights reserved.
 > --------------------
 > | From: "Mark Hripko" <mhripko DeleteThis @hotmail.com>
 > | Subject: Where is HTTPODBC.DLL discussed/supported
 > | Date: Thu, 11 Sep 2003 05:36:42 -0700
 > | Lines: 8
 > | X-Priority: 3
 > | X-MSMail-Priority: Normal
 > | X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
 > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
 > | Message-ID: <uXWVcFGeDHA.228 DeleteThis @TK2MSFTNGP11.phx.gbl>
 > | Newsgroups: microsoft.public.inetserver.iis
 > | NNTP-Posting-Host: wsip-24-234-62-223.lv.lv.cox.net 24.234.62.223
 > | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
 > | Xref: cpmsftngxa06.phx.gbl microsoft.public.inetserver.iis:275085
 > | X-Tomcat-NG: microsoft.public.inetserver.iis
 > |
 > | I'm trying to find where people discuss issues with HTTPODBC.DLL the
ISAPI
 > | connector that allows me to have my web pages draw info from the sql
server.
 > | I can't seem to find anything anywhere in either IIS or the SQL SERVER
news
 > | areas
 > |
 > | -Mark Hripko
 > |
 > |
 > |
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Where is HTTPODBC.DLL discussed/supported