In the video Richard takes out "1" and "l" and "0" and "o" out of my code.  It was well worth watching this video for that  suggestion.  I also cut the special Characters to the following "!,@,#,$."   This is not personal information or email addresses.  They represent password parameters.  They are listed on my password screen.  I am not giving away anything my users are not provided.

The video that I provided with the simple encryption was, as I made very clear in the video, just for the simplest of use cases. If you really have a need to encrypt your database and you're storing sensitive information, you really should use SQL Server. It has much, much better encryption. Microsoft Access by itself is not a very secure environment for data. The code I showed is good enough to keep Sue from accounting from seeing some sensitive data, but anyone who knows what they're really doing can easily bypass it.

I'd actually be in interested in Aes255.  Used it with a website a few years ago and wondered many times how hard would it be to implement in Accesss.... yeah I could learn SQL Server but my brain will explode if I do that.

I have a database program that encrypts data.  You need the assistance of ChatGpt.   The U.S. Government uses it.  I could give you some pointers. But not on this  site.  Now my database is a canned stand alone program.  Its not for networked systems. I don't believe there is any SQL lines of code in it. It involves simple VBA code.     I will contact Richard to forward my email address to you.