[AccessD] 2 quick questions

<quote>
And, there would have to be a quick search to see if this id is already present.
</quote>?

Why not just put an index on the ffull name/dob fields or use a hash of that info as a key.  
Then look that  up if you are checking for duplicates.  It dioesn't have to be user readable.

-- 
Stuart

On 27 May 2011 at 10:24, John Clark wrote:

> Well...yeah...they need to know when a child coming in has already
> been there, and what data they provided at that time. 
> 
> And, no, the person entering data does not enter the number/rule...it
> is done automagically after they enter the other data. And, there
> would have to be a quick search to see if this id is already present.
> 
> >>> "Susan Harkins" <ssharkins at gmail.com> 5/26/2011 3:32 P >>>
> Do you really need this though? I mean... how are the users actually
> going to apply it? Are they going to have to memorize your rule and
> enter the string to id the patient?
> 
> Susan H.
> 
> 
> > It is going to be used to track their clients. There are 3 alternate
> > surveys, but I think each one can be given multiple times. They want
> > to track the clients and how their dental visit habits change. So, I
> > asked them if they want to know if these same clients return and
> > they are saying yes.
> >
> > So, if my example Joe T Murphy is entered as a 5 yr old, and they
> > return and take another survey at 10, and then at 15 and finally at
> > 20, they'll need a way to tell that this was the same person each
> > time.
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>