|
>And instead of thinking how I need this data and how simply I could get >all the data with a simple SQL cursor, I now need to do all these COM >calls. For this to work well you need _good_ com objects. The objects should model your business, not your data. Objects almost become hyperlinks to other objects. For example, you could start with an order. Get the Customer object from the order, get the orders collection from the customer, get an order from the collection, get the order lines collection from that order, get a line from that collection, get the item from a line, get the vendor from an item, etc. You could then traverse and access the "data" in your enterprise without regard to how it's stored (or where). Some might be on one system, some on another, who cares. -Walden ------------ Walden H Leverich III President & CEO Tech Software (516) 627-3800 x11 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.