I have found that those types of problems went away when I started using ADO. look here for an example:
http://fox.wikis.com/wc.dll?webtalk~UsingADOCarlKarsten
>Cool... Thanks.. you saved me the trouble of figuring it out. I seem to have run into another small (I hope) problem. When I try to do an insert where postme is greater than 255 chars it don't work either. Any ideas how to get around this one?
>
>>This will fix it.
>>postme=replace (postme,chr(10),"*!*")
>>postme=replace (postme,chr(13),"*X*")
>>
>>Of course you can use whatever you want as a replacement, I just used these.
>>
>>HTH
>>Jeff
>>
>>>AH HA!! I figured out something very odd.. It works for me on one condition (which I bet you did) If you never hit the enter key while typing in the textarea box it works great, but if you hit enter it gives an error.. so something about the enter key puts something in the code that causes the ODBC driver to go postal. If yuo want to test this and let me know if you receive the same results it would be great.. also I pulled out the line that said
>>>postme=Server.HTMLEncode(request.form("post"))
>>>that caused the html to display as text on the page that displays what is in the table.. I guess I could have HTMLdecoded (if it exists) but I pulled the line and it works fine.. Altough I would like to figure out a way to pull out whatever hitting enter puts into the string. Oh well this will work for now, I'll just tell everyone (only 2 people will use this) to not use the enter key.. Thanks again for you help.
>>>
>>>
>>>
>>>>Not a lot of options to play with on the dsn I don't think? Maybe its something to do with IIS or the service pack level. I'm not sure, but darn thing works great here.
>>>>
>>>>Jeff
