>Jojo,
>
>I don't know what your application does, but how on earth can one Form use >or process 21,000 records?

Hi Bonnie,

Isn't it thats how a disconnected datasets works and designed to?

>You don't need to retrieve the entire table into one DataSet. You pull down >what you need, as you need it. Here's an example:

Thats my point ever since, using a datasets without filtering result sets is no good, thats the reason also i dont want to use datasets when inserting, updating and deleting records, instead i use SQL statements. But if you tell me that you're using datasets even inserting records without fetching any records then that would be ok. I can easily understand & accept it.

BTW, if you know how an insurance company do their business, then you know already what our application does.


>
>Say I have a Personnel module in my application. First, I would present >some sort of search mechanism to the user for them to be able to specify >which Personnel they wish to look at. It may be something as simple as >having the user specify a last name, then retrieve a list of Personnel >that match that name into a DataSet to be presented to the user in order >that they may select which one they want to look at. Notice that I do not >need to pull down the entire list of Personnel into a DataSet ... only a >small sub-set based on the search criteria.

>This is acceptable to me, thats why i mentioned earlier on this thread that >i'll might use datasets only on enqueries.


Anyway, thank you very much, i have a clearer idea now how to make use the benefits of using datasets.

God bless...

>
>Once they've chosen a name, I go back out to the database and retrieve all the information for that one person into another DataSet to be displayed in the Personnel Form. Notice that this Personnel DataSet can contain several different tables, if you wish, corresponding to several tables in the backend database.
>
>My point is that is that it is not necessary, not practical and not desirable to retrieve every record in a table to be presented to the user.
>
>~~Bonnie
>
>
>
>
>>Hi Alex/Bonnie,
>>
>>Ok, so it means that performance wise, still better using SQL select statements to fetch records down the client than using a dataset that has no filter. But, using disconnected datasets in an application and bring the data and travel to other countries or out of town, datasets is the best. (still has draw backs.)
>>
>>We do a test on our project and imported a 21,000 records to our Clients table. On opening a form which uses datasets to fetch the recods and work locally, it takes less than two minutes to show the form with a P4 2.8 GHZ @ 512 MB and same when closing the form.
>>
>>So my opinion on using DATASETS W/OUT filtering records when fetching from the outlying DATABASE/DATASOURCE is non-sense. Even using a good business/data access layer, you have to pull all available records from the database to the datasets isn't?
>>
>>Instead of rolling out our finish application in two weeks time, we decided to change the way how we pull data from the database and works locally, and for adding new transactions why I should I used DATASETS?
>>
>>I hope that your experienced using Datasets were different compared to me :).
>>
>>Anyway, since I'm a newbie on datasets, im still exploring the benefits in software app development.
>>
>>Thanks.
>>
>>>>Talking of Datasets, if let say I have a PolicyHolder table with 50,000 records, how can I pull all the records and disconnect from my Database from C#/VB.NeT?
>>>>
>>>>Can you explain as there might be difference between a Datasets created with Delphi/Interbase and C#/VB/MS SQL.
>>>>
>>>>I just need an answer, please.
>>>>
>>>>Thanks.
>>>
>>>
>>>Should be no different. You connect to the DB using the proper driver oir provider. Doesn't matter if it's SQL Server or Interbase. Any of the examples and connextion strings you can get online would work. Once you run your query and obtain a DataSet (although 50,000 records is a little to many to bring all at once), then you close the connection and you have a local DataSet to work with. Not as powerful as with VFP, but C#/VB.NET can do a lot with it.