It was my mistake, the databaseManager.getDataSetByQuery(…) wouldn’t load the records because it didn’t met the where clause. (note to myself: check that first next time…)
Funny part is that the controller.loadRecords(…) loaded the records even when the query should not find records with the given where clause…
Anyway, the getDataSetByQuery(…) is of no use to me, it doesn’t allow to create records. I wanted to use it to prevent the annoying “flickering” of the user interface.
anton.dorrestijn:
Funny part is that the controller.loadRecords(…) loaded the records even when the query should not find records with the given where clause…
Seems strange to us, if the query is wrong or has no results the form shows no records.
Are you sure the query is correct? and does not return results?