Thanks, Dave! I tried your suggestion and it works. However, my problem is
that the names that were already in the Last Name field are not updated to
include the First Name also. How do I do this?
Your suggestion works much better than mine since I noticed when I went back
over my data on my Form that even though the First Name or Last Name was
correct, the corresponding other half of the name may not have been if there
were more than one with the same name, i.e., Michael as First Name or Smith
as Last Name. I am afraid that this would mess up my data if I left this so
I turned all of the combo boxes I had back to Text boxes. I don't like the
Text boxes though because my data could become inconsistent which is why I
wanted to use Combo Boxes instead.
> You really proabably don't need two boxes. I would suggest:
> SELECT EmID, FirstName & " " & LastName AS Full Name FROM tblEmployee;
[quoted text clipped - 21 lines]
> > > column to 2 but the one for First Name doesn't work if I change the bound
> > > column to 3. What am I missing?
Are you saying you are using names from one table to enter into another table?
If so, you really should not do that. It violates the data redundancy rules
for database normalization.
The correct design is to carry the name fields in only one table. In the
other table, you would use the EmployeeID as a foreign key and theny use a
query when you want to show the name with the other record.
And, it sounds like you are using the combo as a bound control. So, I need
a bit more detail on what it is you are trying to accomplish, please/

Signature
Dave Hargis, Microsoft Access MVP
> Thanks, Dave! I tried your suggestion and it works. However, my problem is
> that the names that were already in the Last Name field are not updated to
[quoted text clipped - 34 lines]
> > > > column to 2 but the one for First Name doesn't work if I change the bound
> > > > column to 3. What am I missing?
JWeaver - 31 Jul 2008 18:41 GMT
Yes, unfortunately, I have the names listed in 2 tables. I inherited a
database that includes all data in one large table but should really be
broken down into several smaller tables. I have been trying to figure out
the best way to do this.
I have one large Payroll table but I also have an Employees table and a
recently created Clients table. I know that I need to add PK ID fields to
the Employee and Client tables and use these ID's as FK's in the Payroll
table instead of the actual names but I've been afraid to remove the
duplicate values from the larger table for fear that I will corrupt the data
that is already in the table.
I'm considering whether I should start over and create all of the tables I
need from scratch or to just break down the larger table into smaller tables
of related data (maybe using the Table Analyzer as a starting point). One
fear is that I have a great deal of reports already created using the
database like it is and I am afraid that if I start over that I will not be
able to get the reports designed correctly.
What do you suggest?

Signature
JWeaver
> Are you saying you are using names from one table to enter into another table?
> If so, you really should not do that. It violates the data redundancy rules
[quoted text clipped - 45 lines]
> > > > > column to 2 but the one for First Name doesn't work if I change the bound
> > > > > column to 3. What am I missing?
Klatuu - 31 Jul 2008 19:02 GMT
I understand your problem. At this point, remediating such a mess would
actually be a rewrite.
The basic idea to fix your problem is to use the After Update event of the
combo box to populate a text box that is bound to the name that is not
getting populated.

Signature
Dave Hargis, Microsoft Access MVP
> Yes, unfortunately, I have the names listed in 2 tables. I inherited a
> database that includes all data in one large table but should really be
[quoted text clipped - 66 lines]
> > > > > > column to 2 but the one for First Name doesn't work if I change the bound
> > > > > > column to 3. What am I missing?