guys and gals
I have to relate this story -
maybe some of you have had the same experience.
I'm currently doing some contract work which involves adding
some improvements to a project I did a few years ago.
The code and the practices that were used back then are making
me cringe and thank the stars that I've improved quantum levels
since then (I'm sure of it - not boasting). I was one of 3 people
working on this project but at least I was using stored
procedures back then.
Some of the easter eggs I've re-discovered
- Very basic or no error trapping
- Session variables
- inline SQL statements (not mine!)
- command.Parameters.Refresh on *all* the stored procedure calls
- short hand object references eg. rs("Variable")
- generally ugly code modularisation
I'm obviously re-coding/improving in the places where it
makes sense to for future maintenance and isn't too much of an
overhead.
cheers
Don't laugh too hard now - an example for you:
cmd.Commandtext="{call sp_GetGrpVals(?,?,?)}"
cmd.CommandType = 1
cmd.Parameters.Refresh
cmd(0) = AUserKey
cmd(1) = AType
cmd(2) = lsFullGrpName
SET rsgrid = cmd.Execute
euggh!
---
You are currently subscribed to activeserverpages as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
