Refreshing queries from VBA that expect prompted values

Question

Please consider:
Run "SAPBEX.XLA!SAPBEXrefresh", False, SAP01.Names("SAPBEXq0001").RefersToRange
(SAP01 is my code name for SAPBEXqueries.)
Assuming the query requires a date for refresh, I would expect the following to work:
Run "SAPBEX.XLA!SAPBEXrefresh", False, SAP01.Names("SAPBEXq0001").RefersToRange, format(Date,"mm/dd/yy")
but it does not... replying, 'invalid # of arguments'.
So I tried:
Run "SAPBEX.xla! SAPBEXSetFilterValue", Format(Date, "mm/dd/yy"), "", BEXD02.Range("ab6")
(BEXD02 being the codename of the query embedded sheet.)
but no dice.

Answer 1

Pete,
There are a few things I do when first I embed queries.
1) Change CODENAMES based on a simplistic naming convention.
codename for tab SAPBEXqueries becomes SAP01
codename for tab SAPBEXfilters becomes SAP02
codename for 1st tab of queries becomes BEXD01
codename for 2nd tab of queries becomes BEXD02 (Bex data, etc.)
Not to bore you, I bring that up to lead into the following code references.  Perhaps like you, I use a SELECT CASE once a query has refreshed and I'm sure to last implant a query for which workbook dates can be derived. Once that last query has refreshed and control is returned to my project, I use the following to grab the date supplied by the user (RefreshWBDates is a sub that derives a host of dates based on the value passed):
RefreshWBDates SAP01.Names(queryID & "tVARIABLE_ZGVCPPD2").RefersToRange.Cells(1, 2)
(Variables of course are dependent on the query used and I change them accordingly.)
Or for example I want to create a named range based on the headings of a query I might do the following:
[BEXD01].Names.Add "Indices", query.Offset(0, 2).Resize(1, query.Columns.Count - 2)
OK, the last example isn't quite inline with your question but until very recently, 'query' was set according to the following:
Set query = SAP01.Names(queryID).RefersToRange
In this I was again utilizing the named ranges on the SAPBEXqueries page.  Little did I realize I could have just used RESULTAREA instead:)  But actually I never thought to use RESULTAREA because for debugging purposes I wanted to test my code WITHOUT bex so I'd use the reference above like so:
Private Sub TrixBex()
  'No purpose for the range but to satisfy the parameters
  SAPBEXonRefresh "SAPBEXq0017", Range("A1")
  SAPBEXonRefresh "SAPBEXq0016", Range("A1")
  SAPBEXonRefresh "SAPBEXq0015", Range("A1")
end sub
Sub SAPBEXonRefresh(queryID As String, resultArea As Range)
  ProcessQuery queryID, resultArea
End Sub
Private Sub ProcessQuery(queryID As String, resultArea As Range)
dim query as range
  Set query = SAP01.Names(queryID).RefersToRange
'processing...
end sub
But now that I've 'grown', I use the following for my debugging:
Private Sub SeedBex()
  CallBex "SAPBEXq0002"
  CallBex "SAPBEXq0001"
End Sub
Private Sub CallBex(queryID As String)
  SAPBEXonRefresh queryID, SAP01.Names(queryID).RefersToRange
End Sub
Sub SAPBEXonRefresh(queryID As String, query As Range)
  RefreshBexQuery queryID, query
End Sub
Sub RefreshBexQuery(queryID As String, query As Range)
'processing...
end sub
So in essence, I've totally avoided reading from the SAPBEXqueries page completely and instead pull from BEX's named ranges.  Of course, I do that because I've seen a number of SAPBEXqueries pages pooched that totally destroy the linked queries.  But I suppose in the long run doing it this way is probably more bullet proof since the blasted page is undocumented and could change upon any revision. Possible but doubtful the named ranges will ever radically change as you've probably deduced.
No reward points for this post though eh?