[AccessD] Primary Key Violation

Or, how about avoiding the problem in the first place?

I'm assuming that the employee name is only entered once -- the first time
the employee encounters this particular application? Is there anyway you can
just enter all the employee names now -- and then just let them choose
theirs, as suggested below. Of course, that means someone must update the
database when a new employee is hired, but that's not that unusual.

Susan H.


> Gina,
> Not sure I understand everything you're doing here but here's a couple of
> ideas:
> present a listbox or combobox of existing names to choose from, If they
> can't find it then let them add a new name.
>
> If their name exists make them use a middle intial. If that exists make
them
> use the full middle name, if that exists make them add their lucky number
to
> the end, if that doesn't work then make them add their...
> :o)
>
> If this is on their personal PCs add a column to the table which holds
their
> windows login then use that to identify them if its present and then
present
> their full name on the screen in a form they can relate to. (lookup their
> name for them based on windows login). If the login is not present then
make
> them enter a new name.
>
> HTH
> John B.
>
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gina Hoopes
> > Sent: Monday, November 17, 2003 1:53 PM
> > To: accessd at databaseadvisors.com
> > Subject: RE: [AccessD] Primary Key Violation
> >
> >
> > I am actually using an AutoNumber for an ID that links them to the other
> > pertinent tables, but when they go to enter or edit their data,
> > they don't
> > know this number so if they've already put in their data and they
> > attempt to
> > do it again instead of editing what's already there, I can't ask them
for
> > anything but their name to check if they've already entered data.
> >  I'm open
> > to any better suggestions.
> >
> > Thanks for your help,
> > Gina
> >
> >
> > From: "Charlotte Foust" <cfoust at infostatsystems.com>
> > Reply-To: Access Developers discussion and problem
> > solving<accessd at databaseadvisors.com>
> > To: "Access Developers discussion and problem
> > solving"<accessd at databaseadvisors.com>
> > Subject: RE: [AccessD] OT: Primary Key Violation
> > Date: Mon, 17 Nov 2003 11:34:08 -0800
> >
> > Gina,
> >
> > There is no such thing as a one-time use application, trust me.  If it
> > works, they'll want to keep using it.  Do yourself a favor and use an
> > artificial key rather than the staff names.  You can still create a
> > unique key with the name and something like their work phone number,
> > which you should surely be able to collect.
> >
> > Charlotte Foust
> >
> > -----Original Message-----
> > From: Gina Hoopes [mailto:hoopesg at hotmail.com]
> > Sent: Monday, November 17, 2003 11:08 AM
> > To: accessd at databaseadvisors.com
> > Subject: Re: [AccessD] OT: Primary Key Violation
> >
> >
> > No offense taken, Martin, I've seen the carnage.  Fortunately this is a
> > one-time use db that I have to put together quickly and we don't have
> > any
> > staff members with the same name.  This time ...
> >
> > Gina
> >
> > _________________________________________________________________
> > MSN Shopping upgraded for the holidays!  Snappier product search...
> > http://shopping.msn.com
> >
> > _______________________________________________
> > 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
>