The case of the missing combo box data

[Hilary Ostrov]

I have a combo box that has worked quite happily for well over three
years. Haven't looked at the application for a few months, though,
and today I noticed that data one of the two columns in the cbo has
"disappeared".

Here is the SQL statement:

SELECT tblJobsites.SiteID, tblJobsites.[Site Name]
FROM tblJobsites
ORDER BY tblJobsites.SiteID;

Bound Column=1, Column Count=2

Column with SiteID is bereft of data If I set Column Headings=
Yes, I do see the column heading, but still no data in Column 1.

After tearing my hair out for several hours - and noticing the same
problem for other similar combo boxes *and* in earlier versions of the
application, I tried some experimenting. Interestingly enough, if I
modify the query so that SQL is:

SELECT [SiteID] & " " AS Site, tblJobsites.[Site Name]
FROM tblJobsites
ORDER BY tblJobsites.SiteID;

Magically, doctored data in column with SiteID is no longer missing!

FWIW, I'm using Access 2003 (but mdb is 2000 format), recently updated
to SP3 (which may be the cause of the problem?!) with Win XP Home SP2

Can anyone shed any light on why this might be occurring?

Thanks.

hro

 

[Jeff Boyce]

Hilary

There have been multiple postings of issues re: comboboxes "losing" data
after installation of Office 2003 SP3. It sounds like you've found a
work-around that does not require rolling back SP3.

Unfortunately, the combobox problem is not the only issue that SP3 appears
to be causing.

--
Regards

Jeff Boyce
www.InformationFutures.net

Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

 

[Hilary Ostrov]

Hilary

There have been multiple postings of issues re: comboboxes "losing" data
after installation of Office 2003 SP3. It sounds like you've found a
work-around that does not require rolling back SP3.

Unfortunately, the combobox problem is not the only issue that SP3 appears
to be causing.

Thanks, Jeff. At least now I know it's not something I did (well,
other than installing SP3, it would seem!) ... I had Googled before
posting, but obviously I wasn't using the right combination of search
criteria

I hope these issues aren't part of an MS plot to force everyone to
switch to 2007 [perish the thought!]
hro