You're probably better using at least one stored procedure. If it's possible to parameterise it in VB, it'll be possible to parameterise it in a stored procedure. If it's not possible to parameterise it, stick each one in a stored procedure and call it from SQL/another stored procedure.
Yup - you definitely want a stored procedure. You'll be able to pass your parameters and reduce the amount of code. Your worst case scenario should be a main routine taking parameters and another script/stored procedure calling it :
Comments 9
Reply
Reply
sp_appendmystuff(bread,cheese,milk)
sp_appendmystuff(cat,dog,pig)
sp_appendmystuff(wood,brass,iron)
Reply
(this is the first time I've actually used anything harder than queries and simple macros in access so I'm struggling)
Reply
Leave a comment