If you're working in a .NET environment and you just need a select query, I'd suggest bypassing the API entirely for the data retrieval side. Use ADO.NET and work with the returned data in a datareader or a dataset. You can easily "mix and match" direct SQL via ADO and .NET API calls in your code, depending on which is more efficient in a particular situation. As a rule, I use direct SQL for returning data, and the API if any Create/Update/Delete operations are involved, since generally you don't hav e filters active on simple data retrieval (although you'd want to confirm this was the case in your particular situation).
Regards, Jim. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
