I have a problem, Houston

[June7]

This is odd. The only difference I can see between the two posted dbs is the ControlSource properties are bound to fields in the second. Never encountered this before and I don't know why it is happening.

But why are you using ValueList instead of Table as source for the lists? For example, settings for Employee combobox:

RowSourceType: Table/Query
RowSource: SELECT EmployeeID, LastName & ", " & FirstName AS FullName FROM Employees ORDER BY LastName, FirstName;
ControlSource: EmployeeID
BoundColumn: 1
ColumnCount: 2


ColumnWidths: 0";1"
LimitToList: Yes

[Lou_Reed]

Okay, when I am in form view and click on the Combo Box forms I see the Value List instead of the choices that I want to make.

So how do I - when in form view - make it show me the actual choices instead of a Value List code?

That is the question.

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[June7]

Did you try setting the properties as I suggested?

[Lou_Reed]

When I input the values that you recommended:

RowSourceType: Table/Query
RowSource: SELECT EmployeeID, LastName & ", " & FirstName AS FullName FROM Employees ORDER BY LastName, FirstName;
ControlSource: EmployeeID
BoundColumn: 1
ColumnCount: 2
ColumnWidths: 0";1"
LimitToList: Yes


The properties sheet lets me do it. I then switch to form view and click on the down arrow of the combo box
and I get the error:

The record source 22958,70429,27049,28405,24095, does not exist ... It may be misspelled.

go into the property sheet and set the record to a table or query.

I have already set the record source to Occupancies. I am pretty sure it is spelled correctly. I selected it from list in the property sheet.


I am very confused now as to why this is not working.


Respectfully,

Lou Reed

[June7]

They worked for me. Provide db with your attempted changes. Let's see what you actually did.

[Lou_Reed]

Ceil Inn1_Post2.zip

Okay, here is my document. I have one control that is working and one that is not. I am not
sure why. The difference (to save you the trouble of finding it) is in the column count

The one that does not work has a column count of 1 and the one that does work has a column count of 2.

Why it has to have a column count of two is not apparent.

I believe that we are only dealing with one column. The employee ID numbers.

That is one not two.

Any help appreciated. Thanks in advance.


Respectfully,

Lou Reed

[June7]

Why are there two comboboxes for employees? Of course the one with a value list as RowSource and RowSourceType set to Table/Query will error. Delete that combobox.

I do not get error message with the other employee combobox. However, you set the RowSource different from my suggestion. You include 3 fields in the RowSource, mine has 2. If you are going to do different RowSource then adjust the other properties to comply (ColumnCount and ColumnWidths).

If you have EmployeeNumber in front of EmployeeName, user must type or select employee number, not name.

Why build a query object for the combobox - just have SQL statement pull from table as in my example.

[Lou_Reed]

I checked and entered the combo for Processed By. I followed your settings for everything except RowSource. I used the old one. It came from using
the Combo Box Wizard. That is code is theirs, not mine. It (the Combo Box) then worked. I was happy and surprised. I then found my earlier dysfunctional version and put
that on just for comparison. It has been removed.

BTW. I thought the Combo Box Wizard was to take care of all of this stuff. The Combo Box Wizard is abstracted away (to use a current term popular where I work) from the user. Most users will use a Combo Box occasionally. So the Combo Box Wizard is the way to go.

It seems that you must still worry about these little details, but you should not if you use the Wizard. I thought that I used the combo box correctly, but I guess I did not.

I will respond to your third point when I have a chance to consider it.


Respectfully,


Lou Reed

[June7]

As a general rule I don't use wizards because they do stuff I don't like (such as use macros and group controls into a layout).

I manually build so I can get it the way I want it.

Not saying don't use combobox (I would be lost without them) I am saying if you use wizard to build then deal with the outcome.

[Lou_Reed]

Okay, but after you use the Combo Box Wizard which should make things intuitive and easy (for those of us who use combo boxes infrequently) you still have some little nitty-picky things to do. That defeats - I think - the whole purpose of the Wizard which relives the user of small tasks. If you to input the column count and BoundCoulmn, then go ahead and do the whole thing that way. It I defeats the purpose of the combo box to say it make doing complicated tasks easy (if you are willing to accept some generalities) to then turn around and say now do this small stuff or nothing will work.

Any comments.

Respectfully,


Lou Reed

[Lou_Reed]

Okay, I was able to handle Processed By combo code the way I said previously- Combo Box Wizard. That does not work on the Customer and Room # combo boxes. I guess that I must input code there. I was out sick last Friday, but I remember on Thursday telling you that the Combo Box Wizard did it - not me for the Processed By.

I am unable to us the Combo Box Wizard on Customer and Room #. So I must input code in those RowSource: I am unsure how.

Any help appreciated. Thanks in advance.


Respectfully,

Lou Reed

[June7]

I don't know why you are unsure. Think I already described how to build combobox.

[Lou_Reed]

Yes, but I think if you look back that you will see that we disagreed (slightly) on the RowSource code. I used the Combo Box wizard and got my RowSource code
for the Processed By label and text box. I did not use it on CustomerID and RoomID. I am unsure then how to use them there.


Even if I use the Combo Box wizard, I still have to manually enter
RowSourceType
RowSource
ControlSOurce
BoundCoulumn
ColumnCount
ColumnWidths
LmitToList

R,

Lou Reed

[June7]

Okay, set properties for each combobox as needed. Once you learned one should be able to apply the concept to others. I gave you properties for one.

Whatever RowSource you go with (manual or wizard generated), make sure other properties are set compatible.

As I said, I don't use the wizard.

[pbaldy]

Yes, but I think if you look back that you will see that we disagreed (slightly) on the RowSource code. I used the Combo Box wizard and got my RowSource code
for the Processed By label and text box. I did not use it on CustomerID and RoomID. I am unsure then how to use them there.


Even if I use the Combo Box wizard, I still have to manually enter
RowSourceType
RowSource
ControlSOurce
BoundCoulumn
ColumnCount
ColumnWidths
LmitToList

R,

Lou Reed

The wizard sets all of those properties, with the possible exception of limit to list. If you're having to go back and change them after using the wizard, it's because the choices you made within the wizard weren't really what you wanted.