Which still does not return the unique identifier(the value of 
SEQNAME.NEXTVAL) to the CFM page. The lack of returning a the unique 
identifier was one of the big hang ups given against CFINSERT. A simple 
trigger in the database and making sure form fields use the same names as 
columns would make it seem like for simple inserting CFINSERT is just fine 
and dandy.
 And no I do not use CFINSERT :)

 On 5/12/05, Ian Skinner <[EMAIL PROTECTED]> wrote: 
> 
> Or the simplified version of the example
> INSERT INTO tablefoo (id, goo) VALUES (seqname.next_val, 'soem stuff')
> 
> --------------
> Ian Skinner
> Web Programmer
> BloodSource
> www.BloodSource.org <http://www.BloodSource.org>
> Sacramento, CA
> 
> "C code. C code run. Run code run. Please!"
> - Cynthia Dunning
> 
>


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking 
application. Start tracking and documenting hours spent on a project or with a 
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67

Message: http://www.houseoffusion.com/lists.cfm/link=i:11:2622
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/11
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:11
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.11
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to