How about under the Master-Level Tutorials: Generating stored procedures tutorial?
Respectfully, Adam Phillip Churvis Member of Team Macromedia Advanced Intensive Training: * C# & ASP.NET for ColdFusion Developers * ColdFusion MX Master Class * Advanced Development with CFMX and SQL Server 2000 http://www.ColdFusionTraining.com Download CommerceBlocks V2.1 and LoRCAT from http://www.ProductivityEnhancement.com The ColdFusion MX Bible is in bookstores now! ----- Original Message ----- From: "Jeff Fleitz" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, August 31, 2004 11:56 AM Subject: Re: [plum] SP Invocation Errors > I think you should put a Stored Procedures header under Advanced Topics > and put all this stuff we are talking about under there. Intended use, > caveats, etc. > > Jeff > > Adam Churvis wrote: > > >Jeff, > > > >Tell me exactly where in the Plum Help you would have liked to see the > >additional documentation regarding this, and I'll get it in today while I'm > >working on the tutorials. > > > >Respectfully, > > > >Adam Phillip Churvis > >Member of Team Macromedia > > > >Advanced Intensive Training: > >* C# & ASP.NET for ColdFusion Developers > >* ColdFusion MX Master Class > >* Advanced Development with CFMX and SQL Server 2000 > >http://www.ColdFusionTraining.com > > > >Download CommerceBlocks V2.1 and LoRCAT from > >http://www.ProductivityEnhancement.com > > > >The ColdFusion MX Bible is in bookstores now! > >----- Original Message ----- > >From: "Jeff Fleitz" <[EMAIL PROTECTED]> > >To: <[email protected]> > >Sent: Tuesday, August 31, 2004 11:29 AM > >Subject: Re: [plum] SP Invocation Errors > > > > > > > > > >>Adam Churvis wrote: > >> > >> > >> > >>>Jeff, > >>> > >>>These are not intended for direct use, because we don't know where your > >>>variables are coming from (Form, URL, Session, etc.); they are intended > >>> > >>> > >to > > > > > >>>be copied, pasted, and tweaked slightly to suit your application. > >>> > >>> > >>> > >>> > >>> > >>Fair enough, and I suspected as much. But you will want to be sure to > >>state that in the documentation. Right now it is not clear with the > >>documentation incomplete. > >> > >> > >> > >> > >>>"Old" refers to the old value of the editable primary key (so it knows > >>> > >>> > >what > > > > > >>>to lookup). > >>> > >>> > >>> > >>> > >>> > >>Yeah, I know. Again. I just cut and pasted the code into the > >>DeleteAction template (I guarantee you will have people do this) and ran > >>it. There is no reference to a 'Old' variable on these delete forms at > >>all, so it errors out. > >> > >>Jeff > >> > >> > >> > >> > >> > > > > > > > > > > > > -- > _______________________________ > > Jeff Fleitz > Tekquest, Ltd > Integrated Digital Solutions > http://www.tekquest.com > 866.472.5868 > _______________________________ > > >
