If you are asking how you can avoid the errors of inserting a duplicate record:
I would just check if the record exists, and if it doesn't, then insert the record. If you are just doing one insert: the performance hit will be negligable and not even noticed. However: if you are doing 1000s of records: that is another issue. Andy ----- Original Message ----- > Hi, > i hav one doubt...... > > My SQL server Table Structure is like this > > Table_Name > Cloumn1 varchar > Column2 " > Column3 " > > i have given a COMPOSITE-PRIMARY Key in this table i hav got 30 lacs > of Data. > > my Doubt is > Before inserting the Record i am checking for EOF and when it is EOF > i am inserting..... > it affects the perfomance and also i should not(dont have rights) to > use Stored proc its a maintainence kind of project.. > wat can i do ???? > Either trap the Err Number and prompt the Error Message ??? > if that means whether i have to write General funtion and include > it??? > can any help it out --------------------------------------------------------------------- Home : http://groups.yahoo.com/group/active-server-pages --------------------------------------------------------------------- Post : [EMAIL PROTECTED] Subscribe : [EMAIL PROTECTED] Unsubscribe: [EMAIL PROTECTED] --------------------------------------------------------------------- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/active-server-pages/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
