numero = 20041
interpreted = N
texte = >>Has anyone dealt with this? Should I be searching the database to see if >>the record exists before I append to the database? Any help would be >>great. > >That's the best idea, although you might be able to get away with a >different approach: don't put the sku into form variables anywhere -- >generate it on-the-fly at the page that does the Append. That way people >can't back up to previous forms that have embedded skus in them. I am not too sure I follow what you mean by:>don't put the sku into form variables anywhere -- >generate it on-the-fly at the page that does the Append.I am posting the SKU like this:Are you suggesting that I would have the person who fills out the form get a page where they can approve the posting before it goes to the database, and at that point have the SKU generated?What about what Christer Olsson said:>Use a [Replace] context with append=T instead. That way all new records >(SKUs not existing in your db) will be appended and all existing records >will just be replaced.Is this a cool way to do it?? I think it looks real good.- ck_______________________________________________________________ Charles Kline ckline@macsultants.com MacSultants Professional Solutions for Computer Systems
Associated Messages, from the most recent to the oldest:
>>Has anyone dealt with this? Should I be searching the database to see if >>the record exists before I append to the database? Any help would be >>great. > >That's the best idea, although you might be able to get away with a >different approach: don't put the sku into form variables anywhere -- >generate it on-the-fly at the page that does the Append. That way people >can't back up to previous forms that have embedded skus in them. I am not too sure I follow what you mean by:>don't put the sku into form variables anywhere -- >generate it on-the-fly at the page that does the Append.I am posting the SKU like this:Are you suggesting that I would have the person who fills out the form get a page where they can approve the posting before it goes to the database, and at that point have the SKU generated?What about what Christer Olsson said:>Use a [replace] context with append=T instead. That way all new records >(SKUs not existing in your db) will be appended and all existing records >will just be replaced.Is this a cool way to do it?? I think it looks real good.- ck_______________________________________________________________ Charles Kline ckline@macsultants.com MacSultants Professional Solutions for Computer Systems
charles kline
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...