don't worry - I realise what people are going to suggest: - just re-populate the VO with the new (entityCode) property after the insert and pass that back up to the view.
(except that we're not using Mach-II or any other recognised OO framework - it's all pretty much a procedural MVC and passing structs instead of objects) thanx anyhoo (groan - lack of BDUF* strikes again) *http://www.joelonsoftware.com/articles/AardvarkSpec.html On 8/18/05, Barry Beattie <[EMAIL PROTECTED]> wrote: > Hi all > > I've just had to change the flow of part of an app because the > "autonumber entity code" has now been spec'ed (well after the initial > coding - don't ask why!) > > we've been following what tarten and others do in returning true/false > from the DAO for sucess of the operation. > > we now need the new entity code so that when an initial add is done > the entity is then brought up in edit mode for adding more data > (initial add: 40 fields; update: another 60 or so). Think "select > @@identity..." (it's not but that's the sort of process to happen). > this two stage approach for a new entity is very deliberate. > > so the question is: if there's a system generated entityCode needed to > go back to the UI, that's only available when the data eventually hits > the database, what options are available to return this entityCode to > the view? > > Is just what we've done (change the true/false to entityCode/"") the > only way or is there a smarter way? > > thanx > barry.b > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
