CBO lookup field disappeared 1

[colossalUW]

Hi all,

This is a strange issue that I'm not sure how to being troubleshooting.

I have a grant tracking application that has been successfully running on an XP machine for several months. I noticed recently that two of my forms are now not working properly. One form is a standard search/lookup and the other is a query builder.

The lookup form is comprised of several combo boxes each populated with data from the main tblGrants. The user may select one or more fields to search and a listbox at the bottom of the form displays the search results. However, the combo box for the primary key field, GrantNumber, is no longer populated with data. If I click the "Search" button results still appear in the listbox, but the field for GrantNumber is blank.

I would assume this was an issue with the form, however the same thing happens in my query form. This form is similar to the search form, except it allows the user to select data from listboxes (the same data as in the search form), select AND/OR statements, and perform a query. The GrantNumber listbox here also is blank. In the query form though, I am able to click in the GrantNumber listbox and "select" a GrantNumber, even though the listbox is effectively blank. Hitting "Go" after doing so produces normal query results. In fact, I can scroll through the blank listbox as if it were populated and select different GrantNumbers even though I can't see them.

This literally just started happening the other day. I've made no changes programmatically to the application. I did originally create the application with Access 2000 but migrated successfully to 2003.

Any thoughts on what this might be?

Thanks much.

 

[missinglinq]

The upgrade to ACC2003 was a good move; unfortunately, you've apparently also upgraded to the SP3 service pack and it's buggier than the Great Dismal Swamp! One of the most common bugs involves comboboxes disappearing data. The field(s) in the cbo, in the underlying table, have some kind of formatting. This is often the simple > used to force UpperCase. Remove any formatting from the fields and things should work. The only other option is to uninstall Access then re-install up to SP2.

The Missinglinq

Richmond, Virginia

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

 

[missinglinq]

Here's a link to Allen Browne's site where you can find the latest news about these bugs:

http://allenbrowne.com/tips.html

The Missinglinq

Richmond, Virginia

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

 

[colossalUW]

Wow, nice work! That was exactly the problem. I removed the > forcing the capitalization.

Thanks also for the link.

Cheers!

 

[missinglinq]

Glad to help!

Linq

The Missinglinq

Richmond, Virginia

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