Still Struggling...

Just for clarification, in one of my previous posts, when I stated the
following;

However, there is a way to solve both problems, which I should have
mentioned in my last post, but it involves - yes, that's right -
ANOTHER TABLE...AAAAARRRRGGGGHHH! g

You reduce tblEmployees to only those fields that apply to *all* personell
(full time and subs), then you add another table for the data that
applies to only *some* employees, and relate it back via EmployeeID.

I was talking specifically about tables, not forms.

Now that you have moved on to creating some forms, it will be helpful
if you can be very specific in describing what you are doing. There is a
bit more terminology when it comes to forms, and it is very easy for us
to misunderstand what you are doing since we are not there to see it.

As I said before, if you are referring to objects on forms, they are called
controls. Also, it helps if you tell us the name of the form (or forms) you
are working with as well as the name of the table(s) or query(s) that
are the recordsource of the form(s). For example, you said you are working
on frmEmployees, but does this form have a subform? If so, are the
controls (combo boxes) you are having trouble with on the main form or
the subform? What is the Control Source and the Row Source of the
combo box(s) you are having trouble with?

Let's start with that, then we can move on to your other issues.
--
_________

Sean Bailey


"Aria via AccessMonster.com" wrote:

Hi Bruce,
Thanks for the information. BTW, I see what you mean about starting
additional threads. It seems I did it again...sorry about that. I'll try to
keep it straight. :-)
I'm having a bit of a problem.This happened early last week. I don't know if
you read the post where I stated I didn't get a drop-down list for my combo
box. In the beginning it was unbound but since it didn't work as expected, I
figured it should probably be bound so I changed it. I was trying to get a
drop-down list for tblTitles and tblClassifications. Once I created the bound
box, I received the following error message, "The value you entered isn't
valid for this field. For example you may have entered text in a numeric
field or a # that is larger than the field size." It doesn't highlight any
field in particular.
Strange happenings:
1. When clicking through records, the timing is off maybe half a beat.
You'll see the previous records classification or title after I have moved to
the next record but then it changes.

2. The date created field has the date in the first record only. Subsequent
records have the time.

3. Titles aren't in alpha order. I'm sure it's because I sorted it after I
created the combo box but those changes aren't reflected in the list. I think
it would be easier to find titles if it's in alpha order.

4. I input a default value for State but again, those changes are reflected.
It still shows the original input.

I thought it may have something to do with the combo box since the message
appeared right after but not being sure, I took the following steps:

1. Checked tblEmployee and tblSiteEmp. The only # is the autonumber; all
other fields are text.

2. In tblSiteEmps the Address field is listed as 255 so I changed it to
something reasonable. I know it probably wasn't that but since I was already
there, I took care of it.

3. I deleted both combo boxes and re-created them. Same problem.

4. I checked the input mask for the date created field. As far as I can see,
it's correct. It says short date.

I read a post dated 7/2/08 that had the same error message as mine but that
person had code in the AfterUpdate event and their RowSource info was
different so I didn't think I could adapt their answer to my own problem.
It's probably similar though. What do you think?

This may be repetition of what you already know, but it seems you may be
dancing around the topic a bit.

lol Was I? You're probably right.



BruceM wrote:
I've been away off and on, and haven't been following the whole discussion,
but let me mention a few things about combo boxes. A combo box, as has been
mentioned, can be bound or unbound. A search combo box (to find an employee
record, for instance) is an example of an unbound combo box.
A bound combo box need to get its information from somewhere. One
possibility is a Value List. If you have to select one of the five boroughs
of NYC you could just have a list: Brooklyn; Bronx; Manhattan; Queens;
Staten Island.
For the 50 states you may want to show either the full name or the
two-letter abbreviation, depending on the circumstances. In that case a
lookup table is the best choice. You can have the StateID, StateAbbrev,
StateName. All you would see in the combo box is either the name or the
abbreviation (or both, if you like). In any case, only one value will be
displayed after the selection has been made. Maybe you could do away with
the StateID, and store the abbreviation instead since it is unlikely to
change, but the principle remains the same.
Another option is to build a combo box row source based on values already
storred in the field. If the value you want to use isn't there, type it it.
I don't think there is a use for this approach in your database, but it
comes in handy at times. The Row Source is the field to which the combo box
is bound.
If you store the EmployeeID you can view other Employee information as
needed, at any time. Your EmployeeID is stored in each payroll record, but
no other information about you needs to be stored there. EmployeeID is the
link to the rest of your information.
This may be repetition of what you already know, but it seems you may be
dancing around the topic a bit.

O.k., so I lost the struggle. Well, maybe not. I won't ask a question,
just
[quoted text clipped - 123 lines]
gonna
start :- )

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...arted/200807/1

Just for clarification, in one of my previous posts, when I stated the
following;

However, there is a way to solve both problems, which I should have
mentioned in my last post, but it involves - yes, that's right -
ANOTHER TABLE...AAAAARRRRGGGGHHH! g

You reduce tblEmployees to only those fields that apply to *all* personell
(full time and subs), then you add another table for the data that
applies to only *some* employees, and relate it back via EmployeeID.

I was talking specifically about tables, not forms.

Now that you have moved on to creating some forms, it will be helpful
if you can be very specific in describing what you are doing. There is a
bit more terminology when it comes to forms, and it is very easy for us
to misunderstand what you are doing since we are not there to see it.

As I said before, if you are referring to objects on forms, they are called
controls. Also, it helps if you tell us the name of the form (or forms) you
are working with as well as the name of the table(s) or query(s) that
are the recordsource of the form(s). For example, you said you are working
on frmEmployees, but does this form have a subform? If so, are the
controls (combo boxes) you are having trouble with on the main form or
the subform? What is the Control Source and the Row Source of the
combo box(s) you are having trouble with?

Let's start with that, then we can move on to your other issues.


Aria wrote:
Hi Bruce,
Thanks for the information. BTW, I see what you mean about starting
additional threads. It seems I did it again...sorry about that. I'll try to
keep it straight. :-)
I'm having a bit of a problem.This happened early last week. I don't know if
you read the post where I stated I didn't get a drop-down list for my combo
box. In the beginning it was unbound but since it didn't work as expected, I
figured it should probably be bound so I changed it. I was trying to get a
drop-down list for tblTitles and tblClassifications. Once I created the bound
box, I received the following error message, "The value you entered isn't
valid for this field. For example you may have entered text in a numeric
field or a # that is larger than the field size." It doesn't highlight any
field in particular.
Strange happenings:
1. When clicking through records, the timing is off maybe half a beat.
You'll see the previous records classification or title after I have moved to
the next record but then it changes.

2. The date created field has the date in the first record only. Subsequent
records have the time.

3. Titles aren't in alpha order. I'm sure it's because I sorted it after I
created the combo box but those changes aren't reflected in the list. I think
it would be easier to find titles if it's in alpha order.

4. I input a default value for State but again, those changes are reflected.
It still shows the original input.

I thought it may have something to do with the combo box since the message
appeared right after but not being sure, I took the following steps:

1. Checked tblEmployee and tblSiteEmp. The only # is the autonumber; all
other fields are text.

2. In tblSiteEmps the Address field is listed as 255 so I changed it to
something reasonable. I know it probably wasn't that but since I was already
there, I took care of it.

3. I deleted both combo boxes and re-created them. Same problem.

4. I checked the input mask for the date created field. As far as I can see,
it's correct. It says short date.

I read a post dated 7/2/08 that had the same error message as mine but that
person had code in the AfterUpdate event and their RowSource info was
different so I didn't think I could adapt their answer to my own problem.
It's probably similar though. What do you think?

This may be repetition of what you already know, but it seems you may be
dancing around the topic a bit.

lol Was I? You're probably right.

I've been away off and on, and haven't been following the whole discussion,
but let me mention a few things about combo boxes. A combo box, as has been
[quoted text clipped - 29 lines]
gonna
start :- )

--
________________________

Sean Bailey
s b a i l e y 2 8 4 AT e c e n t r a l DOT c o m

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...arted/200807/1

I was talking specifically about tables, not forms.

I'm very sorry; my mistake.

I'm working with frmEmployees with sfrmSiteEmps. The problem appears to be
cboTitleDescription. I deleted the combo box a couple of days ago in trying
to isolate the problem. I saved the form without cboTitleDescription. When I
opened the form today and cycled through the records, cboTitleClassification
appears to work as expected. I then created a new combo box for Title
Description; same error message as before. The Control Source is
TitleDescription. The Row Source is SELECT [tblTitles].[TitleID], [tblTitles].
[TitleDescription] FROM tblTitles; The Column count is 2. The Column Widths
are 0";1". The Bound Column is 1.

Beetle284 wrote:
Just for clarification, in one of my previous posts, when I stated the
following;

However, there is a way to solve both problems, which I should have
mentioned in my last post, but it involves - yes, that's right -
[quoted text clipped - 3 lines]
(full time and subs), then you add another table for the data that
applies to only *some* employees, and relate it back via EmployeeID.

I was talking specifically about tables, not forms.

Now that you have moved on to creating some forms, it will be helpful
if you can be very specific in describing what you are doing. There is a
bit more terminology when it comes to forms, and it is very easy for us
to misunderstand what you are doing since we are not there to see it.

As I said before, if you are referring to objects on forms, they are called
controls. Also, it helps if you tell us the name of the form (or forms) you
are working with as well as the name of the table(s) or query(s) that
are the recordsource of the form(s). For example, you said you are working
on frmEmployees, but does this form have a subform? If so, are the
controls (combo boxes) you are having trouble with on the main form or
the subform? What is the Control Source and the Row Source of the
combo box(s) you are having trouble with?

Let's start with that, then we can move on to your other issues.

Hi Bruce,
Thanks for the information. BTW, I see what you mean about starting
[quoted text clipped - 54 lines]
gonna
start :- )


--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...arted/200807/1

You may need to refresh my memory a bit here. You had m:m relationships
for Employees to Titles and Employees to Classifications, so you have
junction
tables for each of them, is that correct?

Aria wrote:
I was talking specifically about tables, not forms.

I'm very sorry; my mistake.

I'm working with frmEmployees with sfrmSiteEmps. The problem appears to be
cboTitleDescription. I deleted the combo box a couple of days ago in trying
to isolate the problem. I saved the form without cboTitleDescription. When I
opened the form today and cycled through the records, cboTitleClassification
appears to work as expected. I then created a new combo box for Title
Description; same error message as before. The Control Source is
TitleDescription. The Row Source is SELECT [tblTitles].[TitleID], [tblTitles].
[TitleDescription] FROM tblTitles; The Column count is 2. The Column Widths
are 0";1". The Bound Column is 1.

Just for clarification, in one of my previous posts, when I stated the
following;
[quoted text clipped - 28 lines]
gonna
start :- )

--
________________________

Sean Bailey
s b a i l e y 2 8 4 AT e c e n t r a l DOT c o m

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...arted/200807/1

Yes, that's correct.
--
Aria W.


"Beetle284 via AccessMonster.com" wrote:

You may need to refresh my memory a bit here. You had m:m relationships
for Employees to Titles and Employees to Classifications, so you have
junction
tables for each of them, is that correct?

Aria wrote:
I was talking specifically about tables, not forms.

I'm very sorry; my mistake.

I'm working with frmEmployees with sfrmSiteEmps. The problem appears to be
cboTitleDescription. I deleted the combo box a couple of days ago in trying
to isolate the problem. I saved the form without cboTitleDescription. When I
opened the form today and cycled through the records, cboTitleClassification
appears to work as expected. I then created a new combo box for Title
Description; same error message as before. The Control Source is
TitleDescription. The Row Source is SELECT [tblTitles].[TitleID], [tblTitles].
[TitleDescription] FROM tblTitles; The Column count is 2. The Column Widths
are 0";1". The Bound Column is 1.

Just for clarification, in one of my previous posts, when I stated the
following;
[quoted text clipped - 28 lines]
gonna
start :- )

--
________________________

Sean Bailey
s b a i l e y 2 8 4 AT e c e n t r a l DOT c o m

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...arted/200807/1

OK, so what you need to do is use subforms for this. I'll use Titles as an
example. The junction table (tblEmpTitles) stores the data that defines
the relationship, so you add another subform that uses the junction table
as it's recordsource. The junction table should have these fields;

EmpID
TitleID

Now, if you are using the wizard, Access will create text boxes and labels
for each of these fields. I would delete both the text box and the label
for EmpID (it's usually not a good idea to display ID numbers to users) and
the label for TitleID. Then change the TitleID text box to a combo box with
the following properties (if you're not using the wizard, just start with a
combo box to begin with);

Control Source = TitleID (in tblEmpTitles)
Row Source = Select TitleID, TitleDescription From tblTitles OrderBy
TitleDescription
Bound Column = 1
Column Count = 2
Column Widths = 0,1

Now you can manipulate the size an appearance of the subform so that
it appears to be just a group of combo boxes on your form. For example
you might set the width so that it is only as wide as your combo box, and
set the height so that the user could view maybe two or three combo
boxes at once. Other properties of the form you may want to change
might be;

Default View = Continuous
Scroll Bars = Vertical Only
Record Selectors = No
Navigation Buttons = No
Border Style = Thin

This way, when you make a selection in the combo box, the associated ID
numbers will be properly stored in tblEmpTitles, and you have the ability
to assign more than one title to an employee.

--
_________

Sean Bailey


"Aria" wrote:

Yes, that's correct.
--
Aria W.


"Beetle284 via AccessMonster.com" wrote:

You may need to refresh my memory a bit here. You had m:m relationships
for Employees to Titles and Employees to Classifications, so you have
junction
tables for each of them, is that correct?

Aria wrote:
I was talking specifically about tables, not forms.

I'm very sorry; my mistake.

I'm working with frmEmployees with sfrmSiteEmps. The problem appears to be
cboTitleDescription. I deleted the combo box a couple of days ago in trying
to isolate the problem. I saved the form without cboTitleDescription. When I
opened the form today and cycled through the records, cboTitleClassification
appears to work as expected. I then created a new combo box for Title
Description; same error message as before. The Control Source is
TitleDescription. The Row Source is SELECT [tblTitles].[TitleID], [tblTitles].
[TitleDescription] FROM tblTitles; The Column count is 2. The Column Widths
are 0";1". The Bound Column is 1.

Just for clarification, in one of my previous posts, when I stated the
following;
[quoted text clipped - 28 lines]
gonna
start :- )

--
________________________

Sean Bailey
s b a i l e y 2 8 4 AT e c e n t r a l DOT c o m

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...arted/200807/1

I didn't give you all of the information that you requested. The problem is
on the main form. The recordsource, I believe is tblTitles. I think I found
the answer to one of my problems. The drop-list isn't in alpha order because
the sort was based on qryTitles, but the combo box is based on tblTitles.

--
Aria W.


"Aria" wrote:

Yes, that's correct.
--
Aria W.


"Beetle284 via AccessMonster.com" wrote:

You may need to refresh my memory a bit here. You had m:m relationships
for Employees to Titles and Employees to Classifications, so you have
junction
tables for each of them, is that correct?

Aria wrote:
I was talking specifically about tables, not forms.

I'm very sorry; my mistake.

I'm working with frmEmployees with sfrmSiteEmps. The problem appears to be
cboTitleDescription. I deleted the combo box a couple of days ago in trying
to isolate the problem. I saved the form without cboTitleDescription. When I
opened the form today and cycled through the records, cboTitleClassification
appears to work as expected. I then created a new combo box for Title
Description; same error message as before. The Control Source is
TitleDescription. The Row Source is SELECT [tblTitles].[TitleID], [tblTitles].
[TitleDescription] FROM tblTitles; The Column count is 2. The Column Widths
are 0";1". The Bound Column is 1.

Just for clarification, in one of my previous posts, when I stated the
following;
[quoted text clipped - 28 lines]
gonna
start :- )

--
________________________

Sean Bailey
s b a i l e y 2 8 4 AT e c e n t r a l DOT c o m

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...arted/200807/1

I'm really sorry, Beetle. You've lost me. I don't think this is turning out
right on my end. I've tried countless times. I don't see anything that says
Record Selectors. I'll try again tomorrow. Right now, I'm working on a
computer that has Access 2000. I don't know if that makes any difference. If
it does, tomorrow, I'll try on a computer with Access 2003.
I also need to check our discussions to see why we have a junction table for
EmpClassifications. There must be a good reason but it escapes me right now.
--
Aria W.


"Beetle" wrote:

OK, so what you need to do is use subforms for this. I'll use Titles as an
example. The junction table (tblEmpTitles) stores the data that defines
the relationship, so you add another subform that uses the junction table
as it's recordsource. The junction table should have these fields;

EmpID
TitleID

Now, if you are using the wizard, Access will create text boxes and labels
for each of these fields. I would delete both the text box and the label
for EmpID (it's usually not a good idea to display ID numbers to users) and
the label for TitleID. Then change the TitleID text box to a combo box with
the following properties (if you're not using the wizard, just start with a
combo box to begin with);

Control Source = TitleID (in tblEmpTitles)
Row Source = Select TitleID, TitleDescription From tblTitles OrderBy
TitleDescription
Bound Column = 1
Column Count = 2
Column Widths = 0,1

Now you can manipulate the size an appearance of the subform so that
it appears to be just a group of combo boxes on your form. For example
you might set the width so that it is only as wide as your combo box, and
set the height so that the user could view maybe two or three combo
boxes at once. Other properties of the form you may want to change
might be;

Default View = Continuous
Scroll Bars = Vertical Only
Record Selectors = No
Navigation Buttons = No
Border Style = Thin

This way, when you make a selection in the combo box, the associated ID
numbers will be properly stored in tblEmpTitles, and you have the ability
to assign more than one title to an employee.

--
_________

Sean Bailey


"Aria" wrote:

Yes, that's correct.
--
Aria W.


"Beetle284 via AccessMonster.com" wrote:

You may need to refresh my memory a bit here. You had m:m relationships
for Employees to Titles and Employees to Classifications, so you have
junction
tables for each of them, is that correct?

Aria wrote:
I was talking specifically about tables, not forms.

I'm very sorry; my mistake.

I'm working with frmEmployees with sfrmSiteEmps. The problem appears to be
cboTitleDescription. I deleted the combo box a couple of days ago in trying
to isolate the problem. I saved the form without cboTitleDescription. When I
opened the form today and cycled through the records, cboTitleClassification
appears to work as expected. I then created a new combo box for Title
Description; same error message as before. The Control Source is
TitleDescription. The Row Source is SELECT [tblTitles].[TitleID], [tblTitles].
[TitleDescription] FROM tblTitles; The Column count is 2. The Column Widths
are 0";1". The Bound Column is 1.

Just for clarification, in one of my previous posts, when I stated the
following;
[quoted text clipped - 28 lines]
gonna
start :- )

--
________________________

Sean Bailey
s b a i l e y 2 8 4 AT e c e n t r a l DOT c o m

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...arted/200807/1

I'm just sort of popping in as time permits, so this will not be a thorough
reply. Record Selectors is a property on the Format tab of the form's
Property Sheet. If it is Yes you will see a bar on the left side of the
window, with an arrow pointing to the current record and an asterisk for the
new record (in a continuous form). In a single form I think you just see
the arrow for every record.
The drop-down list isn't in alphabetical order because you didn't tell it to
be. In Sean's Row Source SQL there is an Order By statement. This
determines the sort order. If you use a named query as the Row Source there
is an Order By statement in the query. To see the query's underlying
language (I don't recall if you know this), open the query and click View
SQL.
Just to stress the point, the combo box has a Row Source, which determines
the list the user will see when clicking the down arrow. A combo box is a
control that may be bound to a field, so it may also have a Control Source,
which is a field in the form's Record Source. The combo box is not based on
tblTitles, but rather is bound to a single field in tblTitles. When you
make a selection from the combo box, the bound column in the combo box Row
Source is written to the field in the table. If EmployeeID is the (hidden)
bound column, and FullName is the visible column, selecting a name will
cause the associated EmployeeID to be stored in the combo box Control Source
field.

"Aria" wrote in message
...
I didn't give you all of the information that you requested. The problem is
on the main form. The recordsource, I believe is tblTitles. I think I
found
the answer to one of my problems. The drop-list isn't in alpha order
because
the sort was based on qryTitles, but the combo box is based on tblTitles.

--
Aria W.


"Aria" wrote:

Yes, that's correct.
--
Aria W.


"Beetle284 via AccessMonster.com" wrote:

You may need to refresh my memory a bit here. You had m:m relationships
for Employees to Titles and Employees to Classifications, so you have
junction
tables for each of them, is that correct?

Aria wrote:
I was talking specifically about tables, not forms.

I'm very sorry; my mistake.

I'm working with frmEmployees with sfrmSiteEmps. The problem appears
to be
cboTitleDescription. I deleted the combo box a couple of days ago in
trying
to isolate the problem. I saved the form without cboTitleDescription.
When I
opened the form today and cycled through the records,
cboTitleClassification
appears to work as expected. I then created a new combo box for Title
Description; same error message as before. The Control Source is
TitleDescription. The Row Source is SELECT [tblTitles].[TitleID],
[tblTitles].
[TitleDescription] FROM tblTitles; The Column count is 2. The Column
Widths
are 0";1". The Bound Column is 1.

Just for clarification, in one of my previous posts, when I stated
the
following;
[quoted text clipped - 28 lines]
gonna
start :- )

--
________________________

Sean Bailey
s b a i l e y 2 8 4 AT e c e n t r a l DOT c o m

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...arted/200807/1

Thanks, Bruce. I finally found it. I'm still working on it but I think I may
be getting closer. I had to make the combo box because I could not get the
wizard to give me what I think I need. It created 2 scroll bars (1 vertical
and 1 horizontal). I couldn't see the labels and couldn't scroll to the
labels. The horizontal bar stayed even though I had switched it to vertical
only. Should I delete the other combo box we originally made. The one that is
giving the invalid value message? It's now giving me a couple of new messages.

1. Form/subform can't be set to continues veiw. Microsoft will set to single
form.

2. Syntax error in From clause. I double checked to see if I had input
"FromtblTitles" correctly. It seem to be correct so I'm not sure what the
problem is there.

My other question is about the Control Source. I'm supposed to put "TitleID
(intblTitlesEmps)" So that table(tblTitlesEmps) will be referenced? I'm just
trying to clarify because I don't see anything else that refers to
tblTitlesEmps. Or will it be recorded in both places because TitleID is a
field in both tblTitles and tblTitlesEmps?


--
Aria W.


"BruceM" wrote:

I'm just sort of popping in as time permits, so this will not be a thorough
reply. Record Selectors is a property on the Format tab of the form's
Property Sheet. If it is Yes you will see a bar on the left side of the
window, with an arrow pointing to the current record and an asterisk for the
new record (in a continuous form). In a single form I think you just see
the arrow for every record.
The drop-down list isn't in alphabetical order because you didn't tell it to
be. In Sean's Row Source SQL there is an Order By statement. This
determines the sort order. If you use a named query as the Row Source there
is an Order By statement in the query. To see the query's underlying
language (I don't recall if you know this), open the query and click View
SQL.
Just to stress the point, the combo box has a Row Source, which determines
the list the user will see when clicking the down arrow. A combo box is a
control that may be bound to a field, so it may also have a Control Source,
which is a field in the form's Record Source. The combo box is not based on
tblTitles, but rather is bound to a single field in tblTitles. When you
make a selection from the combo box, the bound column in the combo box Row
Source is written to the field in the table. If EmployeeID is the (hidden)
bound column, and FullName is the visible column, selecting a name will
cause the associated EmployeeID to be stored in the combo box Control Source
field.

"Aria" wrote in message
...
I didn't give you all of the information that you requested. The problem is
on the main form. The recordsource, I believe is tblTitles. I think I
found
the answer to one of my problems. The drop-list isn't in alpha order
because
the sort was based on qryTitles, but the combo box is based on tblTitles.

--
Aria W.


"Aria" wrote:

Yes, that's correct.
--
Aria W.


"Beetle284 via AccessMonster.com" wrote:

You may need to refresh my memory a bit here. You had m:m relationships
for Employees to Titles and Employees to Classifications, so you have
junction
tables for each of them, is that correct?

Aria wrote:
I was talking specifically about tables, not forms.

I'm very sorry; my mistake.

I'm working with frmEmployees with sfrmSiteEmps. The problem appears
to be
cboTitleDescription. I deleted the combo box a couple of days ago in
trying
to isolate the problem. I saved the form without cboTitleDescription.
When I
opened the form today and cycled through the records,
cboTitleClassification
appears to work as expected. I then created a new combo box for Title
Description; same error message as before. The Control Source is
TitleDescription. The Row Source is SELECT [tblTitles].[TitleID],
[tblTitles].
[TitleDescription] FROM tblTitles; The Column count is 2. The Column
Widths
are 0";1". The Bound Column is 1.

Just for clarification, in one of my previous posts, when I stated
the
following;
[quoted text clipped - 28 lines]
gonna
start :- )

--
________________________

Sean Bailey
s b a i l e y 2 8 4 AT e c e n t r a l DOT c o m

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...arted/200807/1