"Not a valid Password" error after saving the Backend.

[Sandy1992]

Hi,

First of all, I will take a moment to thank to all the superb people who helped me in my journey till now. I enjoyed it. I came to learn a lot of things in this forum.Thanks a lot.

I am using A2010. Now, I am done with distributing the .accde file to the end Users.
But I faced problem.

What happened was I encrypted my Backend which was easily available to the end user to change.

So I encrypted it with a password. But, after that whenever I tried to open the Front End it is throwing error stating "Not a Valid Password".

I searched regarding, and came across the fact that usually it happens when we try to encrypt the backend.

So, I decrypted the backend. And my frontend started working fine.

Is there any way to protect my Backend?

All types of suggestions are warmly appreciated :)

[jimatqsi]

Sandy1992, did you relink your tables after encrypting the back-end? If you did, does your password include any special characters? Try changing your password to something without special characters to see if that gives a better result.

Jim

[NeoPa]

As Jim hinted, it should work fine for you if you link (or relink) to the BE tables after the password and encryption have been applied.

[Rabbit]

You should also be aware that since you have to supply the front end with the password to the back end, then whoever has access to the front end can get the password to the backend.

[Sandy1992]

Thank you jim, NeoPa & Rabbit for your replies.

>>>Sandy1992, did you relink your tables after encrypting the back-end? If you did, does your password include any special characters? Try changing your password to something without special characters to see if that gives a better result.<<<<

No. After splitting the Database, the table from the front end will automatically link to the Backend , right!
And if we do some deployment we need to go through the whole process of relinking the tables.So, I have not RELINKED the tables.
Yes, My password does included some special characters to make it difficult to crack. Also, I tried some other simple passwords also, but it leads to same issue.



>>>As Jim hinted, it should work fine for you if you link (or relink) to the BE tables after the password and encryption have been applied. <<<<

I have not encrypted my whole Database before splitting it. I just want my "_be" to secure with a password.

So, is their any way to secure my _be file?

[Rabbit]

Nope. If you need real security, you shouldn't use Access. Anything done in Access to secure it can be undone by the user.

That being said, you can make it more difficult for the end user. Read this article: http://bytes.com/topic/access/insigh...atabase-access

[NeoPa]

Sandy:
I have not encrypted my whole Database before splitting it. I just want my "_be" to secure with a password.

There seems to be some misunderstanding here.

While it may not be the most secure setup ever devised, it is perfectly possible to :

1. Create a BE.
2. Apply a password to it such that it is encrypted.
3. Link to any tables of that database from another (FE).
4. Continue to use the linked table just as you would any other sort of table without the necessity to keep re-entering the password.

This doesn't guarantee absolute security, but it does give a higher level of security than not having a password or encryption.

[jimatqsi]

Sandy, if you have not relinked the front-end to the back-end, your front-end doesn't know what the password is. It can't gain access, which is just what you want, actually. So relink the tables. You'll be asked for the password and then all will be well.

Jim