Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[TheBoy]

TheBoy has been quiet today, reckon he forgot to take his laptop into the little boys room 

Sorry, been busy with a work problem...  ...you any good with asp?


As to last night's "sit down" in the little boys room....  ....sweet mother

Contemplating a visit now, but working up a bit of courage first 

These new fangled launguages with never catch on    Happily coding away in rexx here.

asp is old hat now, but thats what this particular app (that I wrote many years ago) uses.

Ran fine on the old W2K/IIS5/SQL2K combo, needs recoding for W2K3/IIS6/SQL2K, probably due to MDAC vers.  Anyway, recoded part of it, but now an innocent updating of a field in a recordset hangs IIS's WP (doesn't crash it, so the debugs are not really showing much).


Tempted to quickly build another server (if I can find some hardware ), try it on W2K8/IIS7/SQL2K8 to see if it is an anomally with the VM its now using.

[cem_devecioglu]

I would recommend using an sql statement instead of a recordset update..in multiuser environments those recordset updates causes real trouble..

create a string variable with some parameters, change according to case change

and process it within a loop.. also writing a log for updated records in another seperate table (with time stamp) is a good practice.. sorry for being nosey

ps: only case if you are loading a large blob object in this case you have to use a recordset.. but even with that you can limit the update statement with where clause..

[TheBoy]

I would recommend using an sql statement instead of a recordset update..in multiuser environments those recordset updates causes real trouble..

create a string variable with some parameters, change according to case change

and process it within a loop.. also writing a log for updated records in another seperate table (with time stamp) is a good practice.. sorry for being nosey

ps: only case if you are loading a large blob object in this case you have to use a recordset.. but even with that you can limit the update statement with where clause..

It uses recordsets, didn't want to drastically re-engineer it to use SQL updates if I could help it, as that would then need to go back and have a load of testing done, plus I don't really have the time to start doing fundamental changes to it.

No blobs, standard, boring fields.  Couple of ntext fields is the biggest.

Just can't work out why updating the 2nd of these ntext fields with *any* value causes IIS to go into a loop awaiting for MDAC to return. This happens at the

rs("field")="Test"

stage, rather than the

rs.update

stage....

[Sixstring]

May as well be talking outer mongolian...........

SQL what???

[cem_devecioglu]

from the pages I've read  I concluded that ntext variable assigments

must be done in a fashion similiar to blobs..

you need to set an object variable pointer to rs("field)

then use appendchunk method - please check this 2 links

http://support.microsoft.com/kb/280514

http://www.tek-tips.com/viewthread.cfm?qid=238401&page=1994



And there are other alternative stored procedure methods but more complicated I'm afraid :-/


http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=12651

http://www.experts-exchange.com/Programming/Languages/Visual_Basic/VB_DB/Q_10264796.html

[TheBoy]

don't need to blob it on sql2k or later...

SPs out of the question, due to fallback running off Access.....

[feeutfo]

anyone know wtf they're on about?