>I have one app that needs lookup data from 37 different lookup tables. All of that is pulled into business objects with strongly typed properties with one call to one sproc when the app starts up. After that I'm working with local cursors on instantiating every control on ever form that needs them - or just using them "under the hood" for calculation or validation.

Exactly what I've always done, Charles ... I use static DataSets for lookups rather than biz objects, but the end result is the same. Chunky vs Chatty.

~~Bonnie



>But that;s the point. In .net you pull the data and you populate the control - seperate steps. Get all the data in one trip, then populate the controls. ADO worlks differently from Fox. There is a lot of power in the disconnected nature of ADO data. You can return multiple cursors with a single sproc - one trip to the server - and then fill multiple datatables from that sproc from which you fill your controls., It is more efficient than 25 trips.
>
>One of the big myths that has lived in our community for too long is that Fox "handles data" better than .NET. Just isn't true. I handles it differently and there are strengths and weaknesses on both sides, but once you really get your head into the .NET way of doing things you'll find the advantages can be very great.
>
>I have one app that needs lookup data from 37 different lookup tables. All of that is pulled into business objects with strongly typed properties with one call to one sproc when the app starts up. After that I'm working with local cursors on instantiating every control on ever form that needs them - or just using them "under the hood" for calculation or validation.