@Schmidt Thank you for your suggestion. I believe I've found a workable solution by creating a custom ID field that generates a random alphanumeric code in the RDBMS so that, when a new record is inserted, the database will automatically take care of this part of it for me (rather than having the application logic generate something and hope that I don't run into a concurrency issue). The function that's written in the database to generate the unique ID will actually loop until it finds one that isn't in use before committing the INSERT.

Thank you all again for the tremendous discussion. It has really shed some light on the whole issue and helped me to work through a number of things rather than banging my head against a wall. I truly appreciate all of the assistance.