Listbox missing field... Only on dev box

[Guest]

Here's a peculiar item.
A few weeks ago, I began reworking a front end mdb and noticed that one of
my listboxes stopped displaying data in the first column of a listbox on one
of my forms.

The data is 'there'. If you look it up in an immediate window using the
column(0,1) reference, the result is correct. The listbox data is populated
via sql line via vba code.
Copy the mdb to another workstation and it works fine.
Bring up a copy of the form from archives/source-safe and the same result
occurs.

The field is a 6 number string. The BE data and table have not been
modified, either.

I have decompiled, used both 2000 and 2003 versions of mdb and mde files. I
have manually ran through the code and

According to the Windows Update history, SP3 installed around the time I
noticed the missing field.

So...Any ideas of what I'm missing? This is code and data that hasn't been
modified for some time. So, the focus has to be what is going on with the
workstation. Its a WinXP-SP2 machine w/ Office 2003, Visual Studio 2003. I
am about to the point of wiping the HD and reinstalling.

BC

 

[Ken Snell \(MVP\)]

By chance, is the field to which the listbox is bound is a text field and
has a Format property setting for the field in the table? And by chance did
you recently update your Office 2003 software to SP3? If yes to both
questions, this is a bug that has been reported by many ACCESS users during
past weeks. It apparently is a bug in Office 2003 SP3, which was released by
MS some weeks 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.

 

[Guest]

There is no formatting associated with the listbox. The data is derived from
a SQL string assigned to the rowsource.
-=> me.lstbox1.RowSource = strSQL
I will keep an eye out for the update.

Thanks for the heads-up. I'll just revert to a pre-SP3 till the updates show
up.

BC

 

[Guest]

Hmmm, Well, I guess I can't simply rollback to a previous version.

I guess the SP3 update would likely be the culprit for my digital signature,
too. I thought I had a corrupted Db when I copied it over to an Access 2K
workstation and kept receiving the "project unviewable" error. The MS help
for this didn't work, though. It seems that you cannot remove a digital
certificate, or, at least not without replacing it with an alternate
certificate.
According to the help, all I needed to do was remove the dig.cert. and
restart the mdb. Well, the next restart, I was not able to view the project
from 2003 access. After a compact & repair, the project was unlocked and the
dig. cert. was restored to the mdb.

I hope the patch is coming down the pike shortly.

BC

 

[Ken Snell \(MVP\)]

"Combo box controls and list box controls display no value or
incorrect values in Access 2003 after you install Office 2003 Service
Pack 3." And a few more problems SP3 introduced.

Description of the Access 2003 post-Service Pack 3 hotfix package:
December 18, 2007 - 945674

http://support.microsoft.com/kb/945674

 

[BC-w2k3s]

Works great. It didn't require a reboot, either. Thanks for the heads-up.

How long does it usually take for escalation from the hotfix to offical
patch in an ms-update event?

Thanks again, Ken.

Happy New Year.

 

[Ken Snell \(MVP\)]

Hotfixes are not part of the normal "ms-update" process. Normally, they're
rolled into the next SP release. However, because there will not be an SP4
release for Office 2003, the hotfix likely will continue as a stand-alone
update that will need to be manually applied (and found in order to do the
applying).
--

Ken Snell
<MS ACCESS MVP>