ADO Stream Object sorts the field order - why?

[Jon von der Heyden]

Hi All

A little while back Andrew showed me that using the ADO Stream object I could preserve the recordset filter. I am using this:

Public Function FilterRecordSet(ByVal objRecordSet As ADODB.RecordSet, ByVal strFilterText As String) As ADODB.RecordSet
    Dim objStream As ADODB.Stream
    
    On Error Resume Next
        objRecordSet.Filter = strFilterText
    On Error GoTo 0
    
    Set objStream = New ADODB.Stream
    With objRecordSet
        .Save objStream, adPersistXML
        .Close
        .Open objStream
    End With
    
    Set FilterRecordSet = objRecordSet
End Function

This seems to order the fields alphabetically. Do you know how to avoid this, or do you know an alternative way to use the filter method on a recordset and dump the filtered results (without looping through all records)?

 

[Jon von der Heyden]

Thanks Rory. I really appreciate it. This isn't a show stopper but unless I can get to the bottom of it, it will cause me a bit of rework...

 

[RoryA]

Just sent you an email. If you change the cursorlocation of the recordset to use a client side cursor, then the problem is averted.

 

[Jon von der Heyden]

Sweet! What made you think of that?

Edit: I'm moving this to public forum. I don't think this topic has been covered before so I imagine it may help someone some day. I only posted in MVP forum because I knew Rory would get to it this way.

 

[RoryA]

It was the only obvious difference I could see between what you were doing and what I had done. Still not really sure why that should make a difference and I didn't actually test the saved output to see if that was in alphabetical order, or if it was reloading it that made the change.

 

[Jon von der Heyden]

The outputs are perfect now. I don't either get why it should make ablind bit of difference but for now I don't care; just happy that it works. I've already moved onto my next snag (stupid string field contains mix of #'s and text and throws mismatch when converting to array). Grrr! Anyway I think I have work-around for this.