Sorry if I am whining, but I have come a problem, and there seems to be no help out there.

To start, I did the Access security seminar in its entirety. I did it on 2010.

So using the techniques, I built my own database (and even that worked for a little while.)

Then it started prompting for a password when creating the table links for the back end (as opposed to getting them automatically from the Global variable.)

After hours of research, and weeding though tons of gibberish and registry editors, I couldnt find a solution to this problem. I took the password off the backend database and it works fine.

I put the password back on and I got the error Encrypting with a block cipher is incompatible with row level locking. Row level locking will be ignored.

Now I dont know what row level locking is, and it would appear that access doesnt either, because the only thing I can find has to do with record-level locking (which honestly I am not sure what that is either.)

So my next paper-thin lead was that it may have something to do with folder permissions. I tried every file sharing technique I could dream up, and nothing worked.

Finally, out of shear desperation, i created a new user account on my computer, and started from scratch with the seminar (very useful I might add, because Richard is a phenomenal teacher!) However, this problem is still here, and I am dying to hear any new suggestions anyone might have. And sorry again for the rant, I am just that frustrated.

I did forget to add that I have a 32 bit vista machine and I moved the DB onto that with the same result/

---

Reply from Richard Rost:

That's very interesting. Yes, "row-level" and "record-level" locking are the same thing. Does everyone who has access to the database have full READ/WRITE permission to that folder? Are you using mapped drive letters or UNC paths like //SERVER/DATA/?