List and repeating container

[Alan Lander]

I am trying to build my first web application, and I am not familiar with coding. I have am using now a desktop application first developed in 2002, updated four years ago. In the desktop version of what I use there is a dbf table called clients, with a primary key. When a client is searched the client address, birthdate etc. fields appears. There I is also browse that populates from another set, showing all the files associated with that client, one client can have many files, with the link being client id.

I have in my playing around with the web version of the application a list control, with search part, and when a client name is clicked in the list, fields on the ux component are populated with data from the client table (now sql table running on a MySQL database server). I then have repeating container with the file information, still linked by client id. The fields in the repeating component are bound to the table file, and the parent/child link was set up.

I have no idea of where or what the code is to populate the repeating section when a client is chosen from the list. I tried something in the server side events, tried something on the click the column properties in the list control, and am not getting it. Looked for videos, documentation - knowing this must be a very simple thing to do.

Sorry for what seems to me is probably a very, very basic question -any help will be, well, helpful.

[alexc]

Hey Alan,
If data is bounded to the ux you want to run an action javascript "Populate Controls in a UX Component with data from Tables" from say an onSelect or onClick event within the list builder

[CharlesParker]

If I were you I would stay away from repeating sections at all costs. It is FAR easier and superior (to me anyway) to use another list control instead. All you have to do is choose the linking fields and the parent list. There are lots of different ways though. You could also create another component and embed it, then the embedded component can filter by an argument. The argument's value can come from a field in the current list so that in effect your able to open another component and filter based on the current record.
Lastly, with all of the options involved, just know that it isn't a basic question!

Repeating sections work with databinding of the UX not the list control - it wouldn't surprise me if you could do it BUT that's the general rule.

To get what your after, create a second child list. I think you will find that to be really easy to do.


If you go the Grid route, you can use linked grids in much the same way. Personally, I find myself moving away from grids but for certain things they are just easier to build and complete with a lot less options for you to botch it - but again, I think the list control is the best.

Good luck!

[alexc]

Great explanation charles. Right on point that this opens a whole decision tree of choices to go down. I tend to use grids for fast data entry if the intended user is on a desktop, otherwise everything else is ux with list controls coupled with viewboxs, forrmviews or stamdard controls.

[Alan Lander]

Thank you. Adding a second list was simple- ultimately. The ultimately was that it was not working at first. I looked finally at the linking table on my SQL database. It had not transferred data correctly. I transferred the data and everything worked. I look at this as the same as forgetting to plug in the computer thirty years ago when my staff had no idea on how to work the new machine that replaced the IBM typewriter on their desk! I have to get use to checking the SQL server to make sure it is OK as well.

There is a learning curve and I am just at the beginning. The good news is besides everything working OK.

Again, thank you for the responses.

[asap rich]

Hey Alex! When you say you are using formviews, and viewboxes...what are the advantages of those over lists and grids? I still haven't figured out when and where to use those controls.

[alexc]

I have realised this thread is in V11. So features of the viewbox and formview are probably not applicable. but here is my answer anyways

One - I use the viewbox when i don't need the features of a list likke saving back to the database. I use it to solely display data without all the css and footprint the list has
Two - I use viewbox in conjunction with a listbox and bind the data of the viewbox to the list data soucre. Usually in layouts that sit side by side as clearly dont need a second list
Three - I tend to have both List and Viewbox on my components. Very rarely i would just use a viewbox.
Four - The viewbox and list have different ways of dealing with each record in the HTML Template. What i mean is that list will display each record depending on your setting either vertical, horizontal or snaking, the view box will do anything you define in the HTML template along with some CSS.

With the formview control (this is essential a viewbox with additional features to speed the dev up of Forms). Again i would use i conjunction with a listbox with a detail view.