no warnings for duplicated values

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I set up a table with an id number as primary key and shouldn't allow duplicated values in it. I designed a form based on this table and everytime that I input a duplicated value (which i may not know it's duplicated) the form does not alert me to this fact. If I close the form, it will close normally and will ignore the data. So in fact it's not allowing me to insert duplictaed value but it's not alerting neither that is a duplicate nor that will ignore that entry. This is really important, please help.
 
I set up a table with an id number as primary key and shouldn't allow duplicated values in it. I designed a form based on this table and everytime that I input a duplicated value (which i may not know it's duplicated) the form does not alert me to this fact. If I close the form, it will close normally and will ignore the data. So in fact it's not allowing me to insert duplictaed value but it's not alerting neither that is a duplicate nor that will ignore that entry. This is really important, please help.

It sounds like somewhere along the line (in code or in a Macro) you
have used DoCmd.SetWarnings False and then not set the SetWarnings
back to True.
 
Cannot figure out how to turn on setwarnings... Any clue? Also for some reason the table is not allowing me to change the ID number. I have identified some ID numbers that are wrong and then tried to change but no success. It says that other tables are related. Any clues??
Cheer

----- John Vinson wrote: ----

On Mon, 8 Mar 2004 08:21:11 -0800, "crabello
I set up a table with an id number as primary key and shouldn't allow duplicated values in it. I designed a form based on this table and everytime that I input a duplicated value (which i may not know it's duplicated) the form does not alert me to this fact. If I close the form, it will close normally and will ignore the data. So in fact it's not allowing me to insert duplictaed value but it's not alerting neither that is a duplicate nor that will ignore that entry. This is really important, please help.

It sounds like somewhere along the line (in code or in a Macro) yo
have used DoCmd.SetWarnings False and then not set the SetWarning
back to True.


John W. Vinson[MVP]
Come for live chats every Tuesday and Thursday
http://go.compuserve.com/msdevapps?loc=us&access=publi
 
Back
Top