Search results

thanks Josep Which applicaton hav I to use? ...how can I do?

thanks arnelgp, this is perfect!

no ...I'm unable to do this code mods in right way

accdb

BE is password encrypted. Ok The problem is that FE password is know by the client users, It is not possible to hide the FE password because the client users cannot work anymore on FE…. It is right? It would be great if client users can do only the login into the Fe login form and work in the fe...

if someone could fix it and reupload the file it will be great! Thanks

Multi-user application

I need just to protect my data as much as I can :) Nothing else :) Anyway I think, in my case It should be already protected from a standard - normal user. I asked only your opinion about this :) Thanks

First of all: the tables, then the db itself, if it will be copied into another pc (be+fe) it must not works!

Ok, so the weak of db “fe+be” is the easy way to enable shiftkey when Fe starts. When fe is started with shiftkey all tables are visibles…

Also if I write a “peronal code” that disable shiftkey at startup?

You’ve right! And this is why I’ve removed on FE shifkey + all navigation panels… It is easyto enable shiftkey at FE ? That’s why I would prefer a “personal” code that disable shiftkey than the access file that autodisable shiftkey, you have posted and I’ve used

Also if the BE is under password it is simple to access at table data?

First of all: the tables, then the db itself, if it will be copied into another pc (be+fe) it must not works!

I forgot a thing: If login is correct, the FE has a VBA code that check if file xxx is present into a determinate folder, if there isn’t that file the applications ends.

Hi at all, I would like to know your opinion about how much safe is my FE + BE. I try to explain: With this forum's help, I've removed the shifkey at startup at my FE. (when Fe opens, It has a login form with password) BE has a password I've setted in Access main options. I've set also a...

Yes but I hope someone here that has access 64 may fix this little "browse problem"!

I used wildcard characters both for my FE and BE DB... so it didn't works at all! Using "normal" characters it is ok! .... for the FE the shiftkey is finally removed!! For the BE It says it has been removed, but for BE shiftkey is always enabled. Pheraps the BE doesn't have code so de shiftkey...

this is the pop-up error if the target is a FE DB. If the DB is not splitted all is well done!

I've compiled now (from vba-no errors), but nothing change