I hve a built A CRM to include contacts calls leads and projects.

I have created user login with password that opens with the DB

1 How do I now create a DB lock out with wrong password info

2 Create a Macro or True false relationship with the user name and password to only allow that use to add and edit their contacts,calls, leads, projects with a read only on all the other information.

My goal will be to split the DB with user login in to a FE when they login they go to a custumized dashboard for that user (this currently happens)

my issue is they can close the login with out entering user or password and gain access to all the forms and they are able to change edit other users entries using the forms and queries even after loging in.

please any help on any of this would be greatly apreciated

I would split the database ASAP. You will then need to fully test your database to be sure that everything works correctly. Be sure to put eh back end on the server to test performance.

I wrote this article on the subject: Splitting your Access database into application and data

Here is an example of a login is system: Boiler Plate Database

Hope this helps ...

__________________
Boyd Trimmell aka HiTechCoach (.com)
Microsoft Access MVP Alumni 2010-2015

I need to create the working BD before I Create a FE BE its easier to add items and test .at this point no one is working in the DB other then me.

Any Idea on the user login issue. I know it can be done but how is my issue

I have to disagree. You can not properly test the database until it is split and the back end is on another machine.

If you know all the things to avoid when designing a split database then you might not having any problems once you split it.

I find just way to many advantage to having a database split from the start.

Without seeing you database it is really impossible to spot the issue.

Designing a security system is not a easy task to do correctly.

Implementing a security system after a database is completed can be done but it is a lot more difficult. Unless you have already planned for it in your initial design, it often requires some redesigning of objects and work flow to get the security system working properly.

Did you get a chance to look at the example?
Did it give you any ideas?

In what mode are you opening your log on form?

__________________
Boyd Trimmell aka HiTechCoach (.com)
Microsoft Access MVP Alumni 2010-2015

I did go to your example. It looks good How did you get the login to work.
I created a Employee table with passwordID as my Primary Key. Then linked that to my login form.

The dasboard is good and I may design parts of mine to be more button friendly but currently its a Navigation form.


We may want to create a share point at some time but not yet( I am creating all Macros so that when and if we do we will not have any code issue'

The login, Not sure what you mean by Mode. I created a form Login then put it in the options display form when open after entering user and password the form closes and opens a personal Dashboard.

This is not a fully working DB. I am creating it now (but I may take your advise and copy my DB before I split it )splitting it now is premature in being that I am using 2010 to create it and all of my users do not have Access 2010 so when I split it I will be creating A accbe (not sure that is the correct lettering I will be formating it so that Access 2010 is not needed to use the FE)

Ohhh .. trying to do security with just macros.

I have never using just macros. I have always used code modules to make it hard to crack.


Are you opening your logon form in dialog mode?

You will probaly need to be sure to trun off the control box and close butten etc to try to force the user to click you commnd button.

You will need to also stop alt-F4. You proably will need to use teh autokeuys macro for that.

Unfortunately ACCESS WILL ALWAYS BE REQUIRED to run your front end (.accdb, accde, accdr). If the users do not have Access installed then you will have to install some version of Access. Either the full retail version or the runtime version.

It sounds like you are probably planning on using the Access Runtime. I deploy ALL my front ends with Access running in runtime mode or with the runtime.

To be able to properly test you database for running as a ACCDE with the Access runtime you really need to split your database and compile the database into an ACCDE. Otherwise you can not properly test. You will also need a machine with the actual runtime installed to be sure that every things works correctly. There are things that work in an ACCDB that will NOT work in an ACCDE or in the actual Access Runtime.

My opinion is that it is NEVER to premature to split your database. Especially if you are deploying a front end as a ACCDE and/or using the runtime.

__________________
Boyd Trimmell aka HiTechCoach (.com)
Microsoft Access MVP Alumni 2010-2015

I need to set the user options or defiintions so that one user can not edit or change another users data assigned to them only be able to read.

Thanks for all the help I have alot of good input to apply to my DB.

I am going to search the term Dialog mode, Being fairly new to all this I do not know the term or options. What mode would you suggest I use

Since you are new to all of this I would urge you to spend some time studying the example database. It will teach you a lot about doing what you want.

Have you looked at the design of the log on form in the example?

Do you have the Sharepoint Enterprise edition required for publishing Access databases?

Curious, have you actually published an Access database to Sharepoint?

__________________
Boyd Trimmell aka HiTechCoach (.com)
Microsoft Access MVP Alumni 2010-2015

Is there do you have a second admin password to unlock the design?

I like the login design, But I did not see how you placed the form in the load on start. I see you did not got to the options.

No we do not have the software yet. I have to sell the oldtimers on the DB being accessable from our server with FE loaded on our desk tops before they will ever sign off on a web based application.

Id love to check out your example but I can't navigate past the Dashboard to look at the forms design or formulas.
am I missing something?

Hold down the shift key while opening the database to bypass the autoexec macro.

To help you better, would you mind sharing your programming skills and background. What is your database design background and experience?

__________________
Boyd Trimmell aka HiTechCoach (.com)
Microsoft Access MVP Alumni 2010-2015