Thanks David,
Having become used to the "You just do it this way" flexibility of LLBLGen I was expecting it to be an oversight of mine
It appears that the method you suggest would indeed return the data I need, but to have this value returned automatically during (for example when using databinding) I would have to hack the generated code to call this function instead of the built-in one, as the default routine is called automatically by the Lazy-load routines.
I did consider using Prefetch to grab the associated records, but with 32,000 People records that would add quite an overhead, particularly if the user only selects one or two Customers. That many rows wouldn't normally be a problem, but this database is no rocket, and data transfer requests need to be kept to a minimum
Not having write access to the database is quite crippling, as almost all of the LLBLGen functionailty is dependant upon existing views to manipulate data.
In my case I would love the facility to provide a subquery as a view name, then I could refer to it with its modified and joined fields as a TypedView.
Has anyone worked out a way of doing this?
Cheers,
Jason