Forums

Hello,

I would like to better understand the difference between using DB Multi Record Loader and the Chrono Connectivity Task under the ChronoForms Apps section.

For example, I have a form that has a single drop down menu where a user selects a category. I have used the DB Multi Record Loader in the onSubmit section to display all the records defined by the category parameter sent to it. I have also used the Chrono Connectivity Task in the onSubmit section to do the same thing. Note, I'm not using them both at the same time. I have been experimenting with them to try to understand them better.

I have read the FAQ on the DB Multi Record Loader but I still don't think I understand either of these functions well enough to know when I should consider using one instead of the other.

Would you help me by clarifying what circumstances I might consider using either one?

Many thanks for your help.

Hi Chris,

I'm not sure that there is a black and white line between them.

Broadly if you want to get a set of records back from a database table (or a join of two or three tables*) to use in a form - say to populate a select drop-down. The use the DB Multi Record Loader.

If you want to display the results as a simple** list then use the Data Displayer options.

At the other end of the spectrum, if you want to build a form based application that included lists to select and filter data and forms to view and edit them then ChronoConnectivity is the tool to use for the lists. It is enormously more powerful than the DB Record Loader - but also more complex to understand and use.

In between - it all depends on what you need to do and what you are familiar with.

Bob

* If it's more complex then I'd hand-code a query using a Custom Code action.

** If it's more complex then you can use a Custom Code action to pre-process the results and a Custom Element element to display them in a table.