Jojo,
OK, maybe I've misunderstood you ... are you saying that Delphi/Interbase (of which I obviously know nothing about) is a developer environment just like .NET? And are you talking about the data you get through that developoer environment versus the data you get in the .NET developer environment? If that's the case, then of course the "datasets" would be different. That's like comparing a VFP cursor with a .NET DataSet.
I thought you were talking about accessing data in .NET. I'm sorry if I've misunderstood what you were saying.
~~Bonnie
>>Jojo,
>>
>>
>If thats the case, then I think I had mis-understood the book I have about datasets?>>
>>Either that or the author of the book doesn't have a clue! <g>
>>
>>
>BTW, I think there is a difference between a datasets created with Delphi/Interbase and C#/VB.NET/MS SQL. But to conclude on this, I have to finish exporting Interbase Tables into VFP tables, strip duplicate data and migrate/upsize to SQL Server 2005. I'll post the difference if really has.>>
>>No, the DataSet wouldn't be any different. A DataSet is a DataSet.
>
>Well, its true, a dataset is a dataset but I think I have to make it clear what I mean "difference" and I mean datasets created with Delphi/Interbase and C#/VB.NET/SQL SERVER Application, the way how records are filled to a Datasets and how they are pulled down from the datasource to the client PC.
>
>If you have coded Delphi/Interbase, you might know what im saying here, eventhough I'm a newbie, I have coded both C#/VB.Net/SQL 2005 and Delphi/Interbase app and I'm comparing this two.
>
>>It doesn't matter where the data comes from. Here's a little snippet for >retrieving a DataSet from a SqlServer database:
>
>
>>
>>
>>public DataSet GetMyData()
>>{
>> string TestConnection = "server=(local);database=MyDataBase;uid=sa;pwd=MyPassword";
>> SqlDataAdapter da = new SqlDataAdapter("select * from bob", this.TestConnection);
>> DataSet ds = new DataSet();
>> da.Fill(ds, "MyTable");
>>
>> return ds;
>>}
>>>>
>>Now, if you weren't using SqlServer, you'd use the proper connection string for the other kind of database, plus you'd use the OleDbDataAdapter instead of the SqlDataAdapter:
>>
>>public DataSet GetMyData()
>>{
>> string TestConnection = "MyDelphiConnectionString";
>> OleDbDataAdapter da = new OleDbDataAdapter("select * from bob", this.TestConnection);
>> DataSet ds = new DataSet();
>> da.Fill(ds, "MyTable");
>>
>> return ds;
>>}
>>>>
>>In either case, the DataSet object remains the same ... same DataSet, same DataTables, same DataRows ... only the data itself will be different.
>>
>>How was it explained in your book?
>
>About disconnected datasets? Isn't it ADO.NET uses disconnected architecture? And DataSet is at the core of ADO.NET? If you say both yes, then it should be self explanatory.
>
>Thanks
>>~~Bonnie
