Hello Frans,

i really enjoy reading the threads in this forum and I wish each vendor would invest half the time that you do in giving support! Keep it up [don't halve ]!

Are there any issues in using Typed Lists vs Typed views ? Besides the obvious issue if the db supports creating views - what other things are there to consider?

Also, is there another way using entities and showing their related fields in a 1:1 relation (t_employees and t_logininfo) where the employees are bound to a datagrid (I'm using devexpress) and each row should show the fields fo both tables?

Chaim

chaimweb wrote:

Hello Frans,

i really enjoy reading the threads in this forum and I wish each vendor would invest half the time that you do in giving support! Keep it up [don't halve ]!

My pleasure

Are there any issues in using Typed Lists vs Typed views ? Besides the obvious issue if the db supports creating views - what other things are there to consider?

Not necessarily, though it depends on how the view is stored and if you are on a database which stores view queries as compiled queries or not. SqlServer for example copies the view query into the final query, so you don't win anything, though on db2 it can make a difference I think. Also, if you use an indexed view, which stores the view results in the database, it can make a big difference.

Also, is there another way using entities and showing their related fields in a 1:1 relation (t_employees and t_logininfo) where the employees are bound to a datagrid (I'm using devexpress) and each row should show the fields fo both tables?

Grids can only bound to a collection, so if an entity in a collection bound to teh grid has a 1:1 relation with another entity, the grid won't show that entity, as it's not in a collection.