Wrapper a DataTable object, showing a Recordset interface (_recordset)

Question

0.00/5 (No votes)

See more:

in my researchs to find out methods for transformation the DataTable objects in Recordsets objects, all code found presents poor scalability, provocating crash application(out of memory, commonly).
so, I want experiment wrapper a DataTable object and show a Recordset interface (_recorset).

I need to use existing components, made in. NET, in vb6 grids (old application). By transforming the "DataTable" object in the "Recordset" object, from about 3000 records the system lacks memory. The VB6 application is old, I want to use components .NET without changing the structure of this application, which has hundreds of clients using. As the transformation of "DataTable" in recordset not offer scalability, I'm wanting to create a class that encapsulates a "DataTable" object, and through interface, offers an object "recordset".

Posted 3-Dec-10 6:04am

Júlio César de Carvalho

Updated 6-Dec-10 23:30pm

v5

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2010-12-03T15:47:00

I can only guess at what you're really trying to do and what you mean by "horrible performance".

A DataTable object is OK, but if you're processing a large number of records, using a DataReader offers a lot more flexibility and much greater performance than interating over a set of records in a DataSet. And without "wrapping" a DataTable in an outdated structure like a RecordSet object.