That should be OK. Does the name display correctly when you switch to the
SQL's datasheet view? Is the combo box bound to a field, or is it an
unbound combo box that causes another field to be updated?
I don't understand what you mean by "it displays the name differently than
when updated from any other process". What displays the name differently?
The combo box? If so, what other processes update the combo box?
Are you storing the employee name, or the ID number?
I can't think of any reason based on what you have written why you are
having this problem, but it could be that something else is going on to
affect how the name appears in some cases.
As an aside, maintenance could become a problem over time if InBasketName is
a combination of first initial and last name, or something like that. You
should store the names, and concatenate, etc. to get them to appear as you
wish.
> SELECT EmpRoles.EmpID, EmpRoles.InbasketName FROM EmpRoles WHERE
> (((EmpRoles.Role)="LCSpec"));
[quoted text clipped - 20 lines]
>> >
>> > Thanks
cmw - 10 Mar 2008 11:12 GMT
Yes, but because it made me look further only to find that someone had
entered a second record with a different empid and the name without an
apostrophe in the emproles table. The name actually displayed twice, but I
didn't notice that because of the size of the dropdown and the number of
candidates.
Regarding the aside, both the empid and inbasketname are stored (not
something I usually do) but in this case because ad hoc reports are generated
and combined with data from another system, I need to store the name as it
appears in the other system. The inbasket name is not a concatonation, it's
the name as it appears in the other system.
Thanks -
cmw
> That should be OK. Does the name display correctly when you switch to the
> SQL's datasheet view? Is the combo box bound to a field, or is it an
[quoted text clipped - 39 lines]
> >> >
> >> > Thanks