asked on

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?

ASKER CERTIFIED SOLUTION

Scott McDaniel (EE MVE )

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

VirtualKansas

ASKER

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