Hello,
I have currently have a networked Help desk Database that the users log in using their actual name. Once they log in, it "Bumps" their name against the master table to see if there are any open cases that have their name associated with it. If there are, then it prompts them to review those cases. I have just got word from headquarters that they want all names to be first name last, last name first. (Which is the reverse of how I actually have it now) Is there a way that they can continue to use the same user name, but have some coding reverse the name? (To where it would show their last name first?)
Part of the reason this is an issue is once a user opens up an entry form to create a new helpdesk case, it automatically places their username in the "Received By" field. At that point, it now associates that case with their username.
If coding isn't necessarily the best route, do any of you have any ideas or better routes to take?
Thanks,
---roystreet
I have currently have a networked Help desk Database that the users log in using their actual name. Once they log in, it "Bumps" their name against the master table to see if there are any open cases that have their name associated with it. If there are, then it prompts them to review those cases. I have just got word from headquarters that they want all names to be first name last, last name first. (Which is the reverse of how I actually have it now) Is there a way that they can continue to use the same user name, but have some coding reverse the name? (To where it would show their last name first?)
Part of the reason this is an issue is once a user opens up an entry form to create a new helpdesk case, it automatically places their username in the "Received By" field. At that point, it now associates that case with their username.
If coding isn't necessarily the best route, do any of you have any ideas or better routes to take?
Thanks,
---roystreet