Hi,
My Database will be deployed to each of our 5 manufacturing processes, and
each process have their own login/password (setup from the Security Wizard),
how can i set each user a default menu bar? i was thinking of doing it with
the login code.

If CurrentUser() = "Blending" Then
DoCmd.OpenForm "frmSwitchBlending"
>>>>Can i put some kind of setmenu code after this?

Thanks

Craig wrote:
> Hi,
> My Database will be deployed to each of our 5 manufacturing
> processes, and each process have their own login/password (setup from
> the Security Wizard), how can i set each user a default menu bar? i
> was thinking of doing it with the login code.
>
> If CurrentUser() = "Blending" Then
> DoCmd.OpenForm "frmSwitchBlending"
>>>>> Can i put some kind of setmenu code after this?
>
> Thanks

Actually each user should have their own "front end" on their own
computer linked to the data on the "back end" located on the server. (I am
assuming they are not all using the same computer.) Take a look at the idea
of "splitting" a database. It is a procedure designed for just this kind of
situation and has many more advantages and will help you avoid many possible
problems.


--
Joseph Meehan

Dia 's Muire duit

Tom Wickerath wrote:
> Joesph,
>
> Splitting an application is definately something that should be done
> for a robust multi-user Access application. However, unless you, as
> the developer wish to be burdened with creating custom FE files for
> each group (ie. "Blending", "QC", etc.), splitting alone is not the
> entire answer.

I agree that there are times when it is a good choice and times when it
is not. I would appear IMO that this was a case where it should be
considered. I may or may not be a good idea. I may not have made that as
clear as I should have in my original message, thanks for helping clarify
it. It might not even be a good idea for this application.

>
>
> Tom Wickerath
> Microsoft Access MVP
>
> http://www.access.qbuilt.com/html/ex...tributors.html
> http://www.access.qbuilt.com/html/search.html
> __________________________________________
>
> "Joseph Meehan" wrote:
>
>> Actually each user should have their own "front end" on their own
>> computer linked to the data on the "back end" located on the server.
>> (I am assuming they are not all using the same computer.) Take a
>> look at the idea of "splitting" a database. It is a procedure
>> designed for just this kind of situation and has many more
>> advantages and will help you avoid many possible problems.
>>
>>
>> --
>> Joseph Meehan
>>
>> Dia 's Muire duit

--
Joseph Meehan

Dia 's Muire duit