Hi Taco,
you don't drop it you alter it, i.e. ALTER procedure etc.Yep you can do that. I just tend to drop and create as that way I have one sql file that can be used on a database containing the sp and on an empty db [ie when you move the code/db to production]. I know you can detect to see if it exist and either create or alter it but it tends to make the SQL script a little harder to read/longer.
I've run into a few issues in the past with dba's transferring database's between machines but forgetting to transfer the stored procedures.
You can also put the SP creation scripts in a CF page so there's no need to access the db remotely and/or to get round firewall issues. Doesn't work so well with Oracle though as you have to strip out all of the new lines from the SP to get it to work.
Justin ============================================= Justin Mclean Class Software Phone: (02) 93321230 9 Chapman St Fax: (02) 93321032 Surry Hills Mobile: 0416 119 342 NSW 2010 =============================================
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
