Re: Moving memory recordsets from ADO 2 to ADO.NET - correction
- From: "Garry" <garryx@xxxxxxxxxxx>
- Date: Sun, 18 Dec 2005 16:30:00 +0200
Adrian Hi,
A correction.
The recordset which is the result of an application wide calculation is
initialised and then many valuse may be accrued to a specific record. This,
it seems to me would be tracked by a DataTable. How do you tell it in code
to immediately accept changes?? Is this an external parameter or a method
that must be called for each update???
Garry
"Adrian Moore" <queryadataset@xxxxxxxxxxx> wrote in message
news:%23nmq%23A2AGHA.412@xxxxxxxxxxxxxxxxxxxxxxx
> Garry,
>
> Use DataTables to store your data and build DataViews to index and allow
> databinding to display controls.
>
> You can minimize the memory used for changing tracking by always accepting
> changes. If it turns out later that your application can benefit from
> change tracking, this is one complicated piece of logic you won't have to
> implement.
>
> Is your concern about a DataTable being 'weightier' more about the
> additional processing power needed to maintain a DataTable or about the
> memory is consumes?
>
> Ad.
>
>
> "Garry" <garryx@xxxxxxxxxxx> wrote in message
> news:e5sIbCuAGHA.2040@xxxxxxxxxxxxxxxxxxxxxxx
>> Hi,
>> I am rewriting a medium to large financial application from VB6 to
>> VB2005.
>>
>> I use memory recordsets which are build dynamically in code and are
>> sorted
>> using different sort keys embedded in the fields definitions,.
>> (Collections
>> will not support multiple keys.).
>>
>> These memory recordsets are part of the complicated logic used to display
>> grids to the user using tree displays etc.
>>
>> In ADO.NET, I do not see a parallel object. A DataTable is much more
>> complicated as it tracks changes, (I think). I have seen code examples to
>> build a DataTable in code from scratch BUT this would be a much
>> 'wieghtier'
>> structure.
>>
>> As part of the redesign of the application, I want to build a User
>> Control
>> that would be based on the GridView, (or a more extensive third party
>> control), with memory recordsets to store information about columns and
>> rows
>> so it is important to get the correct implementation in ADO.NET.
>>
>> Does anyone have any practical ideas????
>>
>>
>> Garry
>>
>
>
.
- References:
- Moving memory recordsets from ADO 2 to ADO.NET
- From: Garry
- Re: Moving memory recordsets from ADO 2 to ADO.NET
- From: Adrian Moore
- Moving memory recordsets from ADO 2 to ADO.NET
- Prev by Date: Re: Moving memory recordsets from ADO 2 to ADO.NET
- Next by Date: Re: Datagridview new row
- Previous by thread: Re: Moving memory recordsets from ADO 2 to ADO.NET
- Next by thread: Re: Datagridview new row
- Index(es):
Relevant Pages
|
|