Hi loathe, I've considered that and the problem is in the last paragraph of my original post. That is I'm inputting into a db table that drives another application and I'm leary about changing anything in the constraints that may affect the way the other application interacts with it. It has it's own requirements and presently the first two columns:
email_news_list_id email_add are defined as the primary key. I'm not sure I can touch this. In the end if I MUST, I MUST! But I'd like to think that there is a CF-based approach so that I don't screw up the sending of the newsletter twice a week. It's kind of a small window to work in. Jerry >Why not just add a unique constraint to the row in the table, wrap the query >in a try and catch and handle it that way? I mean, let DB 2 handle it you >know what I mean? > >Also, with the submissions being that close together I don't think it's a >human, I'm thinking it's a bot of some sort submitting that form. > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:254404 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
