[RBASE-L] - RE: How can make this code better ?

[Marc]

Hi Karen

Eqnull is ON and my Select that compares the first 4 columns to look for Dups 
should
have found the problem.  I really do not think they double entered the data.

It is like they started the process, then hit ESC then ran the code again.

Thanks
Marc

  ----- Original Message ----- 
  From: [EMAIL PROTECTED] 
  To: RBASE-L Mailing List 
  Sent: Tuesday, February 26, 2008 10:23 AM
  Subject: [RBASE-L] - RE: How can make this code better ?


  One thing to remember is that Delete Dups will not work if any of the columns 
are null, if you have your EQNULL setting as off.  This behavior changed during 
one of the version changes, don't remember when.   So to be on the safe side, 
you should set EQNULL ON before a delete dups if that's not already your 
setting.

  Karen



    HI Adrian
      
    I do not think that is it, I have Delete Dups twice in the code and then I 
run a command
    block that does a Select looking for Dups then pulls the rows up in a Form 
so they can
    be deleted if needed.
      
    It seems like the computer is skipping like old records use to do and the 
Insert daily to
    Hist got 90% done and ran again.  The more I think about how this could 
happen the more 
    mixed up I get, nothing makes sense.
      
    All I know is the code works 99.999% of the time and these once in a blue 
moon things 
    have to be hardware related but if I can find a way to catch this in my 
code that would be
    great.
      
      
    Thanks
    marc