Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 11 total
Thread Refreshing Data Columns Of Dataset
Thu, Feb 22 2018 10:26 AMPermanent Link

Frederick Chin

I have a DBISAM table with 2 fields (1 String,10 and 1 Float) and I created a dataset for it. The DataColumns property show the two fields.

Sometime later, I added another 4 fields and modified the first field to String,50 and the second field to BCD,2.

Is there a way of having the DataColumns property of the dataset refreshed with the updated structure without having to do it manually?

--
Frederick
Thu, Feb 22 2018 11:26 AMPermanent Link

Uli Becker

> Is there a way of having the DataColumns property of the dataset refreshed with the updated structure without having to do it manually?

From the docs:

The following are breaking changes in 2.06 Build 3:
....

The import of dataset columns in the dataset columns editor in the IDE now performs a reconciliation of the columns instead of an outright replacement of the columns. If any columns exist that don't exist in the imported columns, these columns will be moved to the end of the defined columns for the dataset where they can be manually removed, if necessary. If any of the imported columns reside in a different ordinal position in the dataset, the IDE will automatically correct the position of the affected column(s) during the import.

In addition, there is a new reset button that allows you to reconcile the columns using the existing columns in the dataset. The only restriction on performing a reset operation is that the dataset must be defined in the Database Manager. The IDE will always prompt you to select the database where the dataset is defined, but it will first attempt to scan the defined databases to find the proper database and, if it finds it, will automatically select it before prompting you to select the database.

Uli
Fri, Feb 23 2018 5:33 PMPermanent Link

Frederick Chin

Uli,

/*
In addition, there is a new reset button that allows you to reconcile the columns using the existing columns in the dataset. The only restriction on performing a reset operation is that the dataset must be defined in the Database Manager. The IDE will always prompt you to select the database where the dataset is defined, but it will first attempt to scan the defined databases to find the proper database and, if it finds it, will automatically select it before prompting you to select the database.
*/

This is the functionality I was looking for. I did see the button but the hint sounded so dire and the result possibly catastrophic that I hesitated to use it on my production dataset.

Maybe its name should be changed to "Refresh The Items".

--
Frederick
Tue, Feb 27 2018 2:29 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Frederick,

<< This is the functionality I was looking for. I did see the button but the hint sounded so dire and the result possibly catastrophic that I hesitated to use it on my production dataset.

Maybe its name should be changed to "Refresh The Items". >>

That's on purpose - it can result in columns being moved around and changed in ways that may break your application.

Tim Young
Elevate Software
www.elevatesoft.com
Wed, Feb 28 2018 10:48 AMPermanent Link

Frederick Chin

Tim,

/*
That's on purpose - it can result in columns being moved around and changed in ways that may break your application.
*/

I noticed that when the dataset is reset, fields that were present in the DBISAM table still remain in the data columns list.

For example, my table has fields Field1 and Field2. These two fields will be present in the data columns list initially. After I alter the table and remove Field1 and Field2 and add Field3 and Field4, Field1 and Field2 still remain in the data column list together with Field3 and Field4.

Is this intended behaviour?

--
Frederick
Wed, Feb 28 2018 11:25 AMPermanent Link

Uli Becker

<<
I noticed that when the dataset is reset, fields that were present in the DBISAM table still remain in the data columns list.
>>

Just read the docs. Please.
It's all on there.

Uli
Wed, Feb 28 2018 5:11 PMPermanent Link

Frederick Chin

Uli,

/*
Just read the docs. Please.
It's all on there.
*/

I've searched the index for "Reset" and "Reset The Items" and that particular topic is not present.

Could you point me to the section that describes the process?

--
Frederick
Wed, Feb 28 2018 6:25 PMPermanent Link

Raul

Globestar Systems

Team Elevate Team Elevate

On 2/28/2018 5:11 PM, Frederick Chin wrote:
> Uli,
>
> /*
> Just read the docs. Please.
> It's all on there.
> */
>
> I've searched the index for "Reset" and "Reset The Items" and that particular topic is not present.
>
> Could you point me to the section that describes the process?

Release notes is likely what you want

The import of dataset columns in the dataset columns editor in the IDE
now performs a reconciliation of the columns instead of an outright
replacement of the columns. If any columns exist that don't exist in the
imported columns, these columns will be moved to the end of the defined
columns for the dataset where they can be manually removed, if
necessary. If any of the imported columns reside in a different ordinal
position in the dataset, the IDE will automatically correct the position
of the affected column(s) during the import.

In addition, there is a new reset button that allows you to reconcile
the columns using the existing columns in the dataset. The only
restriction on performing a reset operation is that the dataset must be
defined in the Database Manager. The IDE will always prompt you to
select the database where the dataset is defined, but it will first
attempt to scan the defined databases to find the proper database and,
if it finds it, will automatically select it before prompting you to
select the database.

Raul
Wed, Feb 28 2018 7:38 PMPermanent Link

Frederick Chin

Raul wrote:

/*
Release notes is likely what you want

The import of dataset columns in the dataset columns editor in the IDE
now performs a reconciliation of the columns instead of an outright
replacement of the columns. If any columns exist that don't exist in the
imported columns, these columns will be moved to the end of the defined
columns for the dataset where they can be manually removed, if
necessary. If any of the imported columns reside in a different ordinal
position in the dataset, the IDE will automatically correct the position
of the affected column(s) during the import.
*/

Thanks. I think I will gather the release notes into a single file and perform a search there first.

No wonder Uli was frustrated with me for my post.

--
Frederick
Fri, Mar 2 2018 1:52 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Frederick,

<< Thanks. I think I will gather the release notes into a single file and perform a search there first. >>

The release notes are shipped as a self-contained HTML file with every release and linked to from the EWB program group under the Start menu in Windows (called "Release Information" there).

Tim Young
Elevate Software
www.elevatesoft.com
Page 1 of 2Next Page
Jump to Page:  1 2
Image