Regarding Login form

[Kundan]

I want to attach a user ID and password arrangement for my application. It is a split data base. Should the user ID & password table be along with other tables or in some other place? This is the first time I am applying such a thing. Kindly guide me regarding how the security structure should be.

[June7]

Should be in backend.

Access is not easy to make 'secure'. This is a common topic.

[isladogs]

Suggest you look at my password login form example at http://www.mendipdatasystems.co.uk/p...gin/4594469149

All data tables must be in the backend on split databases.

There are many things to consider in terms of security and no Access database can ever be 100% secure
Suggest you read this article on my website http://www.mendipdatasystems.co.uk/c...ity/4594444323.
Using a SQL Server BE will be more secure for your data.

In term of securing the FE, there are many things you should do as well as using password login.
For example, use ACCDE to protect code, remove the navigation pane, ribbon, disable Access special keys including the shift bypass.
Remove Access options to prevent knowledgeable users reversing all of your security measures.... etc, etc

Suggest you also look at my security challenges for ideas http://www.mendipdatasystems.co.uk/s...ges/4594398127

In terms of security, it would be better to not store passwords at all.
Instead check entered passwords against those in active directory if that is in use on your network.
If you have to store the passwords, then they should be encrypted using e.g. RC4 cipher. See my example login for this as well

Good luck

[Kundan]

Suggest you look at my password login form example at http://www.mendipdatasystems.co.uk/p...gin/4594469149

All data tables must be in the backend on split databases.

There are many things to consider in terms of security and no Access database can ever be 100% secure
Suggest you read this article on my website http://www.mendipdatasystems.co.uk/c...ity/4594444323.
Using a SQL Server BE will be more secure for your data.

In term of securing the FE, there are many things you should do as well as using password login.
For example, use ACCDE to protect code, remove the navigation pane, ribbon, disable Access special keys including the shift bypass.
Remove Access options to prevent knowledgeable users reversing all of your security measures.... etc, etc

Suggest you also look at my security challenges for ideas http://www.mendipdatasystems.co.uk/s...ges/4594398127

In terms of security, it would be better to not store passwords at all.
Instead check entered passwords against those in active directory if that is in use on your network.
If you have to store the passwords, then they should be encrypted using e.g. RC4 cipher. See my example login for this as well

Good luck

Thank You! Will try to follow your suggestions. GOD BLESS YOU!!!!

[isladogs]

Good luck and plan carefully.
Whatever level of security you decide to use, remember that you app will only be as secure as the weakest part of your security measures

[isladogs]

Here is another article on my website you may find useful http://www.mendipdatasystems.co.uk/i...ity/4594461803

[Kundan]

Here is another article on my website you may find useful http://www.mendipdatasystems.co.uk/i...ity/4594461803

Thanks a lot! I will be back to trouble you when I face problems implementing all this. GOD BLESS YOU!!!

[Kundan]

Thanks a lot! I will be back to trouble you when I face problems implementing all this. GOD BLESS YOU!!!

How to do the following:
• • Do ONE of the following: o Hide the ribbon
• o Remove Privacy Options from the File menu (otherwise users can undo all the above)
• ​How to create ACCDE file?

[June7]

File > Options > CurrentDatabase > Ribbon and Toolbar Options

However, that will not hide the File and Home tabs. That requires code. I use methods described in: https://support.office.com/en-us/art...a-4e25bc9413de and https://www.accessribbon.de/en/

I also disable function keys and right click shortcut menus as well as the X close.

File > Save and Publish > Make ACCDE

[Kundan]

File > Options > CurrentDatabase > Ribbon and Toolbar Options

However, that will not hide the File and Home tabs. That requires code. I use methods described in: https://support.office.com/en-us/art...a-4e25bc9413de and https://www.accessribbon.de/en/

I also disable function keys and right click shortcut menus as well as the X close.

File > Save and Publish > Make ACCDE

Thanks a Lot! GOD BLESS YOU!!!

[isladogs]

Another method is to hide the ribbon completely. That will also remove the quick access toolbar and the menu bar.
You can also hide the application window if you wish.
See http://www.mendipdatasystems.co.uk/c...ace/4594365418

[Kundan]

Another method is to hide the ribbon completely. That will also remove the quick access toolbar and the menu bar.
You can also hide the application window if you wish.
See http://www.mendipdatasystems.co.uk/c...ace/4594365418

If after removing ribbon I want to transfer the application to another system. Will the application work? Or do I have to re-link it to the new environment? If so can I re-link it after the ribbon is removed? What is the solution to this problem?

[June7]

For a split db and users are all on the same network, table linking options:

1. every user must have same drive letter mapping that was set in the original frontend

2. set table links with UNC patch, I use VBA code to accomplish

If users are not on the same network then table links will have to be re-established, which might not be possible with accde file

[Kundan]

For a split db and users are all on the same network, table linking options:

1. every user must have same drive letter mapping that was set in the original frontend

2. set table links with UNC patch, I use VBA code to accomplish

If users are not on the same network then table links will have to be re-established, which might not be possible with accde file

Thanks for the advice! GOD BLESS YOU!!!