Client API v1.2.3, VaultHistoryQueryRequest().

Given:

	VaultHistoryQueryRequest historyQuery = new
VaultHistoryQueryRequest();
	historyQuery.Recursive = true;
	historyQuery.BeginDate = beginDate;
	historyQuery.EndDate = endDate;

	...

	clientInstance.Connection.HistoryBegin(hq, args.HistoryRowLimit, ref
nRowsRetrieved, ref strQryToken);
	VaultHistoryItem[] historyItems = null;
	clientInstance.Connection.HistoryFetch(strQryToken, 0,
nRowsRetrieved-1, ref historyItems);
	clientInstance.Connection.HistoryEnd(strQryToken);

Where do I enforce or activate the date limitation?  I've noticed
VaultHistoryQueryRequest.DateFilterMask (uint) and DateFilterType (int) but
VaultHistoryQueryRequest isn't documented in the API (I know, I know, it's
not officially supported. :)) so I'm not sure as to how to proceed with
DateFilterMask or DateFilterType.  The SQL that executes when the history is
retrieved doesn't have any indication of transaction dates or times in it,
but that could be because the dates I'm passing to VaultHistoryQueryRequest
aren't getting that far for some reason.

I currently have a client side filter working but for large repositories
that will get bulky and inefficient fast.

Thanks.

Brian Schkerke
Lead Developer
NETCO, Inc.
http://www.netcotitle.com
(636) 925 8657