TD-21101: Grid layout view extremly slow SP2 Build 42038

[MSchmidt]

with SP2 Build 42038 switching to the layout of a form is very slow,
if a grid table object is part of the form and if the child grid has many columns


in the sample there are 3 forms
each form only has one object: a grid table with many columns

if you switch from frm1 to frm 3 and back it takes more than 4 seconds til the frm is visible.

at runtime the effect is not visible in this sample, but in our application a form with a grid with many columns is visible after somes seconds
the same application with a child table instead of a grid opens immediately

TD 6.2 win32 app build
Win 8.0 64

Kind regards
M.Schmidt

[VEspinal]

Hi:

fyi, I've logged a defect TD-21101.

Thanks for the information.

Best Regards,
Victor Espinal

[MSchmidt]

Please let us know when this issue will be solved.

For us child grids are slow compared with child tables

The user has to wait some seconds each time a form window with a child grid opens.
This effect is visible at runtime not only at designtime.

It is a problem for our customers. They want child tables back instead of child grids!

Thank you
M.Schmidt

[VEspinal]

Let me check it for you.

Regards,
Victor

[MSchmidt]

any news ?

Performance of a child grid is very slow compared with a child table.


Instead of "Table2Grid.exe" we need a "Grid2Table.exe"
cause our customers are quite angry.

Gupta, please solve this issue.

Thank you
M.Schmidt

[MSchmidt]

no solution in TD 6.3

the child grid instead of child table is the biggest problem for us to move to .net


the combination of the old Gupta child table and mtable is very powerfull.

A child grid has many incompatibilities and has less functionality compared with
the combination as mentioned above.

Now we are waiting since many years for an alternative to the child table.

I talk about years! This is in the IT industry a non acceptable period of time.

Instead of a solution of all the grid problems, again we now have new functionality in TD 6.3 tested by robots and sometimes I believe not by people. (Sorry)
So all the new functions are useless in the daily work for many monthes (or years) till they have to be tested by the customers of Gupta
and in case of a bug Gupta has to fix it.

Ever and ever the same procedure
New functions, missing opportunities and lot of bugs in these functions, problems in somes countries, suddenly old functions don't work as usual
and not fixed bugs like the one in this thread.

And I believe there are more than 10 known child grid bugs or missing functions- some of them known since many months - not fixed till today.

I can accept that is was necessary to supersede the child table with a view to.NET, but till today the child grid is not a substitute for a child table.
Low speed, different behavior and bugs prevent us, to migrate to .NET.
Have a look on Excel export of mtable! Compare it with the poor Excel export built in in the child grid

Our customers don't want to go back and I still believe Gupta doesn't want it too.


So please take care of the child grid and all not fixed defects and other known problems

Thank you
M.Schmidt

[Welskop]

Hello,

I am not sure if my Problem is the same, but I am also having a big performance Problem with grids. But this Performance Problem is only on my new System with Windows 8.1. I have tested a lot and I found out that the function "SALTblPopulate" is the Problem. When I compare the time to fill the grid with data my old System (Core2Duo E8500, 4 GB RAM, Windows 7 SP1 64-bit)) is six to seven times faster than the new System (Intel i7-5820k, 16 GB RAM, Windows 8.1 64-bit).

The application is exactly the same (TD 6.2 SP3r), but only running on different OS Versions and different Hardware. All other applications are running much more faster on the new System as on the old one! So I think this must have something to do with Windows 8.1!

Frank

[MSchmidt]

solved
TD 6.3 SP1 Update1

Thank you
M.Schmidt