Yes you are correct.
My tblUser is on server and I will remove additional PK and set it on Username and will try n let you know accordingly.
Yes you are correct.
My tblUser is on server and I will remove additional PK and set it on Username and will try n let you know accordingly.
I removed PK from additional field in tblUser and set on USERNAME. But still same...Although msg is appearing that new user added but in reality no record saved. I debug and noted that the Expression variable has generated the encrypted password even but not saving at all.
I know that new users are successfully added in my example app that you downloaded
Unfortunately I have no means of knowing what the differences are in your modified version that is preventing it working for you.
I trying to find the error but till not traceable but still no success. Another thought, can I add new user using normal DAO recordset method? I mean if I do this then will there be any on encryption method?
Please advise...
If you add a user using a DAO recordset or, more simply, just by using an append query you will have issues if the default 'not set' password isn't encrypted.
I think you are going to make this more difficult to manage ...and probably less secure ...if you try workrounds to fix your problem
Thanks Isladogs,
I know if both BE and FE are MS Access, it works great. Sir, just a question for my info...have a ever tried keeping this tblUsers on Server and added any new User from Access FE?
Not with this particular app.
However I have other Access FEs with user data including encrypted passwords that are stored on SQL Server backends