> Does anyone have a better way to see if the date > already exists with Access or can tell where my logic is flawed?
hi mike the strategy I prefer is to go ahead and do the insert, then analyse whether it was successful the reason for this is simple, and is based on the assumption that most of your inserts should be successful let's say that out of 100 attempted inserts, 5 will be duplicates in the select-analyse-insert strategy, you will be executing 195 calls to the database -- 100 selects and 95 inserts in the insert-analyse strategy, you will be executing only 100 calls to the database, of which 95 will have been successful of course, this strategy requires that the column was declared as UNIQUE in the database, and also that you are able to intercept the "duplicate insert rejected" error message or status code from the database, and handle it gracefully rudy - You are subscribed to the CFUGToronto CFTALK ListSRV. This message has been posted by: "rudy" <[EMAIL PROTECTED]> To Unsubscribe, Please Visit and Login to http://www.CFUGToronto.org/ Manager: Kevin Towes ([EMAIL PROTECTED]) http://www.CFUGToronto.org/ This System has been donated by Infopreneur, Inc. (http://www.infopreneur.net)
