There's no equivalent to what you're doing in the browse, Gerard (sigh)

If youre backend is SQL Server, I suggest that you query a vew instead of a table, where the view pre-populates all the fields you need from the related tables.





>>Say my main table is a Customer Table, but there could be losts of related tables with 'Lots' of data (e.g. Sales By Week By Customer could have 52 fields for each customer, Busdget by week by customer could have another 52, Units by week by cusotmer could have another 52 etc). On any one site, I might ever only need say week 1 sales for the sake of argument, and I dont want to have to pull 150 fields across.
I know the 'Disconnected' methodology in Dot Net probably makes this near impossible, but I live in hope !!