Access 2103 Web App: Prevent duplicate entries

Grinding out an Access db upgrade to Access web app.  

Original PK in desktop db is now no longer the PK in web app., given the up-sizing uses the record ID as the PK.  May not have the experience for this upsize, but all seems well after some great advices at: http://www.ascassociates.biz/WebApp12_ConvertTables.aspx  Followed to the letter (especially the last paragraph on referential integrity) and all is well.

Now onward; user on data entry in the app., can create duplicates in the field that was the PK.  Minor issue since all still seem related correctly, but will be when running existing  reports on desktop.  The duplicates will deliver bad results.  What is best method to prevent user from creating a new record using an existing records pseudo PK field?

...or better put, ignoring the PK comment:  How to prevent user from entering duplicate data in a given field?
VirtualKansasAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Create a Unique Index on the table and include the fields that make that record unique. For example, if I have a Customer table, and want to be sure that the values of CustomerName + CustomerPhone + CustomerZip are unique, then I'd add those three fields to a Unique Index.

Web App Unique Index
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
VirtualKansasAuthor Commented:
Hi Scott and thanks for reply.  My problem was actually simpler, but you lead me down the right path.  I only have one unique field requirement in the original db design.  Long story, but the original design didn't have table relationships, I added those later but failed to enforce the index/no duplicates on the field.  With your help, we simply applied the index rule and boom, got the result we're after.

Thank you for "Access 101" reminder.  As long as you agree with our method (even simpler than we thought), then case closed, with our thanks.

BTW; really appreciate your responsiveness.  EE in general has been surprisingly unresponsive, the last few weeks.  Been thinking twice about my subscription, but your help has made a bigger difference then you know and restored our faith.  TY
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.