By: David Zeidman

David Zeidman — Tue, 05 Feb 2008 20:14:11 +0000

There are a couple of issues with the solutions above. The first requires that all the items in the sort collection are closed down after they are worked with. What is more I am not convinced they are actually closed down while there is a reference to them in the sort collection. That is why when you shut Raiser's Edge down it complains that not all the objects have had their closedown methods enacted.

The second method works fine if you are a supervisor user. However I have experienced issues if you have restricted rights. You will of course need to have rights to participants and I am not refering to that. I have not done enough analysis to work out exactly which rights affect the code but when I use the second method for a non-supervisor user I get the error message:

General ODBC Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near the keyword 'AND'.

Native error:156

[Microsoft][ODBC SQL Server Driver][SQL Server]The cursor was not declared.

Native error:16945

I have however found a work around that is very good.

Using the IBBSortableDataObjectCursor interface which the cParticipants collection implements I can set my sort field (Participants_fld_DateAdded) and sort direction (descending) so that the code snippet looks like this:

    Dim oSort As IBBSortableDataObjectCursor

    oFilter.CustomWhereClause = " RECORDSID = " & oconstit.Fields(RECORDS_fld_ID)
    Set oSort = oParts

    oSort.SortField = Participants_fld_DateAdded

    oSort.SortOrder = Descending

    bFound = False
    For Each oPart In oParts

etc

Comments on: Filtering and Sorting Participants – Just not Together

By: David Zeidman