🚀 go-pugleaf

> I know it has nothing to do with your problem but I simlpy have to ask how 
> did you create the strongly typed datasets? Did you use XSD.exe to 
> generate them out of an xsd-file and if so what is the parameter to create 
> a strongly typed dataset in Delphi?

Here are the steps-

assuming you are using Northwind database in MS Sql server-

-    Drop a SqlConnection component and set it ConnectionString property to 
something like 'server=localhost;database=Northwind;Trusted_Connection=True'
-    Drop a SqlDataAdapter component, set its selectCommand.Connection 
property to SqlConnection1, also set its SelectCommand.CommandText to 
'select * from Customers; select * from Orders'
-   Open SqlDataAdapter1.TableMappings collection editor from object 
inspector, map Table to Customers and Table1 to Orders, Click Ok
-    Right click on SqlDataAdapter1 and click Generate Dataset, type some 
name (CustomerOrder) for new dataset and ensure "Add this dataset to the 
designer" check box is selected.

Click ok, Delphi will do the rest for you. It will generate xsd file and a 
unit (CustomerOrderUnit.pas) that will include a desendant of DataSet. Its 
great work done and it can simplify coding efforts to a great extent.

I read this from Delphi for .Net Developer's Guide by Xavier Pacheco.

Visual Studio supports visually editing xsd file, adding new datatables, 
removing existing datatables, managing DataRelations etc. There is no visual 
support for it in Delphi, even generated xsd file is not added to the 
project group.


> I had a look after this information for a while but didn't find it. But I 
> read that this private-public problem is a bug that is still to be fixed. 
> So the only option in the moment seems to generate the classes and then 
> stop touching them since you have to change them everytime you create them 
> anew.

I wouldn't mind if Delphi lets me change the generated file (for the sake of 
using DataColumn names directly and avoiding run time overhead). But any 
changes done to the file are lost when you recompile your project. Its same 
as using persistent TFields in normal delphi DataSet  (<= D7) and not being 
able to use Table1Field1.AsString just because it is declared as private.

Pravin