Well, you shouldn't have the username field if it's based on the value of
other fields. Calculated values should never be stored. As fellow Access MVP
John Vinson likes to say "Storing calculated data generally accomplishes
only three things: it wastes disk space, it wastes time (a disk fetch is
much slower than almost any reasonable calculation), and it risks data
validity, since once it's stored in a table either the Total or one of the
fields that goes into the total may be changed, making the value WRONG."
Create a query, and calculate the Username field in that query. Use the
query wherever you would otherwise have used the table. To add a calculated
field to a query, select any empty column in the grid, and type the
following in the Field row of that column:
Username: Left([Firstname], 1) & [Surname]
(Replace Firstname and Surname with the actual field names)
However, that's only part of the problem. Is Username supposed to be unique?
What happens if two people with the same surname have the same initial?
--
Doug Steele, Microsoft Access MVP
(no private e-mails, please)
"Specific User Form Access"