My forms broke after Office SP3 installed

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Michael D. - 14 Nov 2007 14:06 GMT

Office SP 3 was installed on our corporation's PC's last week, and it broke a
database I'm responsible for. I can't figure it out. Several forms that get
info from tables no longer put the values in the various dropdowns. For
example, I have a combo box called cboProjectTitle who's Row Source Type is
Table/Query, and the Row Source is set to SELECT tblProjectInfo.ProjectTitle
FROM tblProjectInfo; . This has worked for over 2 years, and it still works
on a laptop that doesn't have Office SP3 yet, but no longer works on all the
PCs and laptops that received SP3.

The dropdown appears to have Null values in it. If I click the dropdown and
scroll down through, it acts like the rows are there. But if make a
selection, I get an "Invalid Use of Null" error. The dropdown (in this case)
is a lookup with an event procedure to update a text box. I guess what it is
trying to do is put a null value into the text box.

I can't find anything in the SP3 documentation that would explain what is
going on. I have several backups of the database, as well as a local copy on
my hard drive, and all are broken...

Thanks in advance for any ideas you may have! - Mike

Reply to this Message

Allen Browne - 14 Nov 2007 14:49 GMT

There are a few things that are broken in SP3 for Access 2003:

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

2. Access crashes when you assign a table with more than 31 fields to the
RowSource of a combo. Demo here:
http://allenbrowne.com/temp/A2003sp3bug.zip

3. Visual Source Safe has serious problems with A2003 SP3.

Signature

Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

> Office SP 3 was installed on our corporation's PC's last week, and it
> broke a
[quoted text clipped - 26 lines]
>
> Thanks in advance for any ideas you may have! - Mike

Reply to this Message

mscertified - 14 Nov 2007 14:53 GMT

Try running the query independently and see if it creates the recordset you
expect.
I'd suggest always create and save a query rather than put a SELECT clause
in the rowsource. Do you have the number of columns and column widths
properties set correctly?

-Dorian

> Office SP 3 was installed on our corporation's PC's last week, and it broke a
> database I'm responsible for. I can't figure it out. Several forms that get
[quoted text clipped - 16 lines]
>
> Thanks in advance for any ideas you may have! - Mike

Reply to this Message

Michael D. - 14 Nov 2007 15:28 GMT

I guess I should have searched the forums a litle better, sorry.

There is apparently a bug in SP3. In the tables, the format option for the
fields that were not working had a > in them to make them all uppercase.
Apparently you can't have any Format options in text fields due to this bug
in SP3. I removed the > and eveything is working fine.

Kind of funny, I never liked having that in there anyway. A person with a
mainframe background originally set this database up, and it always seems (to
me) that those types always want everything to be in all caps. It was set
for names, project titles, all kinds of stuff.

However, I'm still going to look into doing what you suggested below.

Thanks! -Mike

> Try running the query independently and see if it creates the recordset you
> expect.
[quoted text clipped - 24 lines]
> >
> > Thanks in advance for any ideas you may have! - Mike

Reply to this Message