A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Setting Up & Running Reports
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

"AND" Clause in Filter Makes Unbound Text Boxes "Invisible"



 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #1  
Old August 30th, 2004, 07:03 PM
Smit-Dog
external usenet poster
 
Posts: n/a
Default "AND" Clause in Filter Makes Unbound Text Boxes "Invisible"

I have a report with a bunch of unbound text box controls. The report is
opened, and then I explicitly populate a few text boxes with data:

DoCmd.OpenReport "rptSchool", acPreview, , "(GUID=""" & strGUID & """)"

With Report_rptSchool.Controls
.Item("txtBldgAge").Value = Round(intBuildingAge, 0)
.Item("txtBldgSizeGSF").Value = Format$(lngBuildingSize, "#,##0")
.Item("txtSiteSize").Value = Round(dblSiteSize, 2)
End With

This works great if the Filter property = "", or if the Filter property is
set to a single field criteria during the Report_Open event, i.e.
"(([ConstellationID] in (6)))".

If the Filter property is set to multiple criteria in the Report_Open even,
the unbound text boxes are somehow "invisible". Example: (([ConstellationID]
in (6)) and ([FacilityTypeID] in (3)))

By invisable, I mean that the text box is actually there, and the value is
actually set, but for some reason the Access report rendering engine "blanks"
out the values for these text boxes. I set the foreground and font colors of
the text boxes to cyan/red respectively, and I can see the text boxes on the
report, it's just that the values are invisible. Checking the text box value
properties at runtime with the debug window, it does return the value, so I
know the value is being set in code. And if the Filter ="", it works fine,
and if the Filter = (([ConstellationID] in (6))) or Filter =
([FacilityTypeID] in (3)), it works fine. It just when the Constellation and
FacilityType are combined in the Filter property.

This is driving me batty. Does anyone have a clue what the Access report
engine is doing here?

Thanks!!!

- Bill
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 04:57 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.