Combo Box & Report Questions

  • Thread starter Thread starter ADB_Seeker
  • Start date Start date
ADB_Seeker said:
Your help is much appreciated!
All updates/changes are complete. The Originator field is now numeric/long
integer and links to the ID field in ASSIGNEES table.
I need help with the next steps, please.
Click to expand...

This brings us back to your original question about the code for your combo
box to open the report filtered by the selected ID value. The crucial line
is the one that assigns the WHERE condition to stWhere. I believe the last
time we were looking at this, the statement in question was this:
strWhere = "[ASSIGNEES].[ID]=" & Me!cboSpecEObyAssignee
Click to expand...

But that is not correct, because the field we want to filter is the
ORIGINATOR field of [EO TABLE]. So the statement should be:

strWhere = "[EO TABLE].ORIGINATOR=" & Me!cboSpecEObyAssignee

Try that.
 
You are awesome! It is fixed and works perfectly. Thank you ever so much!!

Dirk Goldgar said:
ADB_Seeker said:
Your help is much appreciated!
All updates/changes are complete. The Originator field is now numeric/long
integer and links to the ID field in ASSIGNEES table.
I need help with the next steps, please.
Click to expand...

This brings us back to your original question about the code for your combo
box to open the report filtered by the selected ID value. The crucial line
is the one that assigns the WHERE condition to stWhere. I believe the last
time we were looking at this, the statement in question was this:
strWhere = "[ASSIGNEES].[ID]=" & Me!cboSpecEObyAssignee
Click to expand...

But that is not correct, because the field we want to filter is the
ORIGINATOR field of [EO TABLE]. So the statement should be:

strWhere = "[EO TABLE].ORIGINATOR=" & Me!cboSpecEObyAssignee

Try that.

--
Dirk Goldgar, MS Access MVP
Access tips: www.datagnostics.com/tips.html

(please reply to the newsgroup)

.
Click to expand...
 
ADB_Seeker said:
It is fixed and works perfectly. Thank you ever so much!!
Click to expand...

Excellent! It took a little while -- and I apologize for the delays in some
of my responses, but it's been a busy week -- but we got there.

You're very welcome.
 
Back
Top