Combo box will not display Primary Key field values? 1

[blacy]

I have a combo box that displays the following:
Project Managers initials (This is primary Key, two digits, caps)
Project manager’s name

The initials are set to the field when selected.

I have been using this for years and all the sudden the project managers initials are blank in the drop down. This is only true for my computer which I have just done an Office update for. All other computers I go to the Initials are displayed. Also the value is not able to be set because I get a "Not in list" when I try to make a selection.

The data source for the drop down is a Select Query. I have tried to recreate the control and had no luck. For some reason Access will not display the primary Key value when it is text as I have. This has been working for years.. I don’t understand what has changed.

 

[GingerR]

What version of Office? What Office update did you do that others have not?
What is the rowsource for the combo box?
What are the properties set to (i.e. Number of columns, columm widths, bound column, etc)?
If you run the query of the rowsource from the properties screen, does it work properly?

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244. Basics at

http://r937.com/relational.html

 

[blacy]

Thank you for your reply GingerR

To answer your questions.

I dont know for sure that the updates caused this but I will try to get this information. I know it would be valuable if this was the cause.

The version of office is 2003 SP3. I believe that I downloaded the Service Pack 3 update.

The row source is a select query based directly on a table.

I have checked to see that the column widths, column count, Etc. are correct. I can actually see the column in the drop down but it is blank. Like I said I have actually been using this control for years and it has worked fine.

The bound column is the first column which is the primary key column. (Initials)

If I view the result of the select query the data is displayed.

Thanks for your help in advance..

 

[wstlaurent]

I'm having the exact same issue. Has anyone gotten to you on this or have you found a solution?

 

[blacy]

wstlaurent

I have not had any response yet. I did find many problems with office SP3 update along these lines. It is the SP3 update that caused this problem. I was able to fix my problem by adding a Null to the end of the SQL statement and the initals are now shown in the drop down list. However, I have found other problems as well.. I would suggest undoing the SP3 update if this is possible. I was thnking of doing a resote point to make this happen. I have also advised my users not to update to SP3.

Let me know if you find any fix for this problem.

 

[Dizy]

Hi Blacy,

I have a client with exactly the same problem. Did uninstalling SP3 work?

Di

 

[wstlaurent]

blacy: When you said "adding a Null to the end of the SQL statement" can you be more specific? Can you give me an example? I'm not a techie. I assume you simply mean take the existing SQL statement and add ";Null" or something like that but not sure if it's formatted correctly using the semi colon.

Thanks.

 

[missinglinq]

Allen Browne explains some of these problems here.

http://allenbrowne.com/tips.html

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!

 

[wstlaurent]

I can't find this specific one on the site

http://allenbrowne.com/tips.html

Do you know exactly where it is on his page?

 

[Dizy]

Definitely would appear to be a problem with SP3 "Ken Snell (MVP)" <kthsneisllis9@ncoomcastt.renaetl> wrote in message news:<#82SG8YAIHA.748@TK2MSFTNGP04.phx.gbl>...
> By chance, the field to which the combo box is bound is a text field
> and has a Format property setting for the field in the table? If yes,
> this is a bug that has been reported by many ACCESS users during past
> week. It apparently is a bug in Office 2003 SP3, which was released by
> MS about a week ago. MS is aware of the bug and is working on how to fix it.
>
> In the meantime, the "complete workaround" is to remove the Format
> property's value from the field's properties in the table's design view.
> Otherwise, concatenating the field's value with an empty string also
> seems to "overcome" the problem.

So if you have a format property set for the field in the source table just take out the format e.g. > to force uppercase - that fixed it.

 

[wstlaurent]

Amazingly enough what Dizy suggested worked. I had ">" in the Firm_Name field format property of my table and that was the problem with field in my combo boxes.

 

[missinglinq]

Which was exactly what Allen Browne said on his site!

The combo goes blank if it's RowSource is a table field that has something in its Format property.

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!