|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
how to change a name in "msysaccounts"?i need to change the name of a user in msysaccounts to reflect her married
name. and i do not understand how this may affect her log-on also, i need to change all the names from first name last name to last, first to conform to application name conventions when "currentuser" method is used to fill in datafields access 2003 You cannot change the usernames. You basically have to delete the user,
create a new user and assign them to the appropriate groups. For the second case, where you want to change all names, it may (or may not) be easier to create a table to store the Access username and a separate field for the 'display name'. Then you can look up the display name as needed. I often create a table with LName, FName, AccessName, etc. Then you can pull any element you need (LName only for example). -- Show quoteHide quoteJoan Wild LarryH wrote: > i need to change the name of a user in msysaccounts to reflect her > married name. and i do not understand how this may affect her log-on > > also, i need to change all the names from first name last name to > last, first to conform to application name conventions when > "currentuser" method is used to fill in datafields > > access 2003 thank you for the help.
but i am still at a impass as to how the "currentuser" method would be impacted by this approach. and what happens to the application log-in?? again, thanks Show quoteHide quote "Joan Wild" wrote: > You cannot change the usernames. You basically have to delete the user, > create a new user and assign them to the appropriate groups. > > For the second case, where you want to change all names, it may (or may not) > be easier to create a table to store the Access username and a separate > field for the 'display name'. Then you can look up the display name as > needed. I often create a table with LName, FName, AccessName, etc. > > Then you can pull any element you need (LName only for example). > > > -- > Joan Wild > > LarryH wrote: > > i need to change the name of a user in msysaccounts to reflect her > > married name. and i do not understand how this may affect her log-on > > > > also, i need to change all the names from first name last name to > > last, first to conform to application name conventions when > > "currentuser" method is used to fill in datafields > > > > access 2003 > > > Sorry Larry, I don't understand your question. You said
"also, i need to change all the names from first name last name to last, first to conform to application name conventions when "currentuser" method is used to fill in datafields" I interpreted that to mean that currently the usernames are in the format of "JoanWild" and you need to change this to "Wild, Joan" so that when you fill in some field using CurrentUser() you'll see the format you want. I was suggesting that you keep the usernames you have, rather than deleting them all and recreating the usernames in the format you want. If you keep the current format, you can create a table of Employees with LName FName AccessName fields. Wild Joan JoanWild When you fill in some datafield in another table with the CurrentUser() function, it'll fill in with JoanWild. When you want to print information, you can include the Employees table in the recordsource, join the AccessName to the datafield in your table and display Wild, Joan instead of JoanWild. Or you can use DLookup to lookup a format you want to see displayed. If you go ahead with deleting usernames, and recreating them, then users will have a new username that they'll have to use to open the application. -- Show quoteHide quoteJoan Wild Microsoft Access MVP LarryH wrote: > thank you for the help. > > but i am still at a impass as to how the "currentuser" method would be > impacted by this approach. > > and what happens to the application log-in?? > > again, thanks > > "Joan Wild" wrote: > >> You cannot change the usernames. You basically have to delete the >> user, create a new user and assign them to the appropriate groups. >> >> For the second case, where you want to change all names, it may (or >> may not) be easier to create a table to store the Access username >> and a separate field for the 'display name'. Then you can look up >> the display name as needed. I often create a table with LName, >> FName, AccessName, etc. >> >> Then you can pull any element you need (LName only for example). >> >> >> -- >> Joan Wild >> >> LarryH wrote: >>> i need to change the name of a user in msysaccounts to reflect her >>> married name. and i do not understand how this may affect her >>> log-on >>> >>> also, i need to change all the names from first name last name to >>> last, first to conform to application name conventions when >>> "currentuser" method is used to fill in datafields >>> >>> access 2003 again thanks - the substitution approach you suggest seems to be the only way
to go. i will replace the "currentuser" method with a function [Flipper()] which will use the "currentuser" method and then convert from fname lname to lname, fname and this will make the cut over painless for the users Show quoteHide quote "Joan Wild" wrote: > Sorry Larry, I don't understand your question. You said > > "also, i need to change all the names from first name last name to > last, first to conform to application name conventions when > "currentuser" method is used to fill in datafields" > > I interpreted that to mean that currently the usernames are in the format of > "JoanWild" and you need to change this to "Wild, Joan" so that when you fill > in some field using CurrentUser() you'll see the format you want. > > I was suggesting that you keep the usernames you have, rather than deleting > them all and recreating the usernames in the format you want. If you keep > the current format, you can create a table of Employees with LName FName > AccessName fields. > Wild Joan JoanWild > > When you fill in some datafield in another table with the CurrentUser() > function, it'll fill in with JoanWild. When you want to print information, > you can include the Employees table in the recordsource, join the AccessName > to the datafield in your table and display Wild, Joan instead of JoanWild. > Or you can use DLookup to lookup a format you want to see displayed. > > If you go ahead with deleting usernames, and recreating them, then users > will have a new username that they'll have to use to open the application. > > -- > Joan Wild > Microsoft Access MVP > > LarryH wrote: > > thank you for the help. > > > > but i am still at a impass as to how the "currentuser" method would be > > impacted by this approach. > > > > and what happens to the application log-in?? > > > > again, thanks > > > > "Joan Wild" wrote: > > > >> You cannot change the usernames. You basically have to delete the > >> user, create a new user and assign them to the appropriate groups. > >> > >> For the second case, where you want to change all names, it may (or > >> may not) be easier to create a table to store the Access username > >> and a separate field for the 'display name'. Then you can look up > >> the display name as needed. I often create a table with LName, > >> FName, AccessName, etc. > >> > >> Then you can pull any element you need (LName only for example). > >> > >> > >> -- > >> Joan Wild > >> > >> LarryH wrote: > >>> i need to change the name of a user in msysaccounts to reflect her > >>> married name. and i do not understand how this may affect her > >>> log-on > >>> > >>> also, i need to change all the names from first name last name to > >>> last, first to conform to application name conventions when > >>> "currentuser" method is used to fill in datafields > >>> > >>> access 2003 > > >
User level security-- do not have necessary permissions
restrict combo box selection depending on user mapped network drive and security error Tab Change Passwords Programically redirecting to different mdw files Password for opening Report Secure back end database user without admin privilleges was able to join his computer to do Open an Access Database from Another UnHIDE a tbl |
|||||||||||||||||||||||