🚀 go-pugleaf

Hi Joanna

Thanks for your reply..

I am not using dataware components..

On the form load I am using TextBox1.DataBindings.Add("Text", ds,
"master.fieldname); to populate the edit boxes on various tab pages...

I am creating the connection, dataset and doing the binding via code and not
via components...

Is this the wrong way of doing things.


Thanks
Ray



"Joanna Carter (TeamB)" <joanna@nospam.co.uk> wrote in message 
news:41d12c6e@newsgroups.borland.com...
> "RayG" <ray@mweb.co.za> a �crit dans le message de news:
> 41d11e3f$1@newsgroups.borland.com...
>
>> Is there anyway that this can be changed or should I loop through the tab
>> pages and set tabcontrols.SelectedTab each page to initialise the data...
>
> The problem is not with the data-aware controls, which IMO are badly
> designed anyway; the real answer is to separate the logic that does the
> creating of the SQL from the UI.
>
> When you create a new record in the dataset, many of the fields are set to
> null rahter than default values. Why don't you cycle through the dataset
> before the edits are shown and set the default values in code ? Then,
> whether the edits are used or not, the fields are already primed 
> correctly.
>
> Joanna
>
> --
> Joanna Carter (TeamB)
>
> Consultant Software Engineer
> TeamBUG support for UK-BUG
> TeamMM support for ModelMaker
>
>