Quote:
>-----Original Message-----
>Hello Derek,
>The best way is to create a key on the JOBS table where
the key is the
>combination of fields that uniquely define the job. A
similar method is to
Quote:
>create an index instead of a key, and set Unique=Yes.
This second method
>allows you to define further functionalities without
altering the table and
Quote:
>key structures you have already defined.
>Both of these methods are preferable to using Dlookup or
something similar
>because it is more reliable. The uniqueness if the jobs
depends on the
>database structure defined once and for all and not on
your coding which
>would have to be repeated many times.
>I hope this helps.
>Jerome Smith
>> I have a table with a list of jobs assigned to an
autoID.
>> I would like to make it not possible for a user to
enter a
>> job more than once. Should I use the dlookup function?
>> If so, how?
>> Any assitance is appreciated,
>> Thanks,
>> Derek Easley
>---
>Outgoing mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.422 / Virus Database: 237 - Release Date: 20-
11-02
>.
>I have added the index feature like you have mentioned,
but I would like to somehow notify the user when they
enter a job no that will be a duplicate. Currently it
won't notify them until, the next record is selected. Any
suggesetions.
thanks,
Derek
Non Duplicate fields