| What is the difference between table column binding and data element column binding [message #1139153] |
Tue, 15 October 2013 15:25  |
 Jan Krakora
Messages: 477
Registered: December 2009
Location: Prague |
Senior Member |
|
|
When you have a table, you can set column bindings on that table.
But it's also possible to set column binding directly on data elements within a table.
What is the difference between these two approaches?
It's markable when you drag a dataset column from the Data Explorer and drop it into a top level table.
It creates column data binding on the table itself an let the data element reference that binding.
On the other side, when you drop the dataset column on a top level grid,
then the column binding is created directly on that data element an not on the grid column binding. I'm confused.
[Updated on: Tue, 15 October 2013 15:26] Report message to a moderator |
|
|
| Re: What is the difference between table column binding and data element column binding [message #1143058 is a reply to message #1139153] |
Fri, 18 October 2013 01:27  |
|
If the grid is not bound to the dataSet, when you drop a data element into it, it will have to have the binding to access the appropriate data. If the grid were bound to the dataSet, it would not create the bindings in the data element, unless the data element used a different dataSet. In a table, you must have a dataSet attached to it, so each data element from the dataSet will not have the bindings. If you were to drop another dataSet's data element into the table, it would be bound to its dataSet. This would create an embedded dataSet.
So, the short of it is, it's best to have the outer element bound to the dataSet if all of the individual elements will use the same dataSet.
Hope this helps.
Michael
Developer Evangelist, Silanis
|
|
|
|
Powered by
FUDForum. Page generated in 0.01188 seconds
] 
Search
Help
Register
Login
Home
