rc11, searches in tabs and related data

since updating to rc11 and sybase a number of my search routines that worked well in rc1o and firebird are failing:

In rc10 I found it was not necessary to load records at the start of the find. In rc11, if I don’t put a controller.loadAllrecords() at the start I cannot get the search to do anything at all. My understanding has been that for a related tab controller.loadRecords() is correct - to load just the records that relate to the main record being viewed.

Additionally, I cannot get a find to locate related data i.e. the main record in table A shows a tab from table B that also contains information related to B from table C. Previously I could search directly for records in table B that contained related data in table C and show a filtered list in the tab on the record for table A. This no longer works - the list simply remains unchanged!

Are there differences in the way that searches are handled between rc10/firebird and rc11/sybase that would explain why these routines are now broken?

drookwood:
since updating to rc11 and sybase a number of my search routines that worked well in rc1o and firebird are failing:

In rc10 I found it was not necessary to load records at the start of the find. In rc11, if I don’t put a controller.loadAllrecords() at the start I cannot get the search to do anything at all.

In rc11 we fix a bug for a sort showing all records when performed after a find returning 0 records… (in this senario a loadAllRecords is now required yes)

drookwood:
My understanding has been that for a related tab controller.loadRecords() is correct - to load just the records that relate to the main record being viewed.

This is correct.

drookwood:
Additionally, I cannot get a find to locate related data i.e. the main record in table A shows a tab from table B that also contains information related to B from table C. Previously I could search directly for records in table B that contained related data in table C and show a filtered list in the tab on the record for table A. This no longer works - the list simply remains unchanged!

I cannot reproduce this in the sample crm soltution, can you?

No, I cannot reproduce this in crm - I will investigate further - if I get anything reproducable I will send.