Page 1 of 5
REVISION OF GRID/BROWSE
Posted: Thu Jul 02, 2015 8:37 am
by brain
I wish that can someone revise the GRID/BROWSE control into like DBEDIT function for less array and less memory to run the application. Tnx and more power HMG & Members!
REVISION OF GRID/BROWSE
Posted: Thu Jul 02, 2015 1:37 pm
by Pablo César
What we have to understand is GRID and BROWSE are different controls.
When you said like dbEdit, must be cleared something: an control for exclusive use for DBFs, right ?
Because dbEdit only works with databases and also it's hard to work on to conciliate both: arrays and databases in GRIDs.
Otherwise Joselito (brain), why are you requesting this ?
BROWSE is deprecated (descontinued) in HMG and not implementations have been done over this control.
My suggestion is to work on the BROWSE or with other similar name for only and exclusive use for DBFs and working similar of TBrowseDB of old Clipper but in this time in GUI. I'm not sure if this is posible and also I do not know if it's worth it considering many users are migrating to SQL usage instead DBFs.
Re: REVISION OF GRID/BROWSE
Posted: Thu Jul 02, 2015 1:59 pm
by Rathinagiri
Showing DBF in a Grid/Browse control is very easy. But, keeping track of the changes (made if any by the user) and saving/rolling back the changes to the DBF is very hard in GUI controls, in which case, we have to maintain two sets of DBF in memory (which would double the memory usage).
As Pablo said, it is one of the reasons people migrate to SQL/record set based database systems.
Re: REVISION OF GRID/BROWSE
Posted: Thu Jul 02, 2015 4:14 pm
by mol
I'm still using dbfs and browse control. I think it should always be updated.
I remember Roberto words, where he turned back from words this control is obsolete.
Great advantage of dbfs is this system is portable.
You can say that sqlite exists, but it hasn't still some types of fields.
Re: REVISION OF GRID/BROWSE
Posted: Thu Jul 02, 2015 5:45 pm
by luisvasquezcl
Estimado Rathinagiri,
el problema de uso de memoria se produce siempre en el grid, ya sea usando array o dbf.
Saludos cordiales
Luis Vasquez
Dear Rathinagiri,
the memory usage problem always occurs on the grid, either using array or dbf.
best regards
Luis Vasquez
Re: REVISION OF GRID/BROWSE
Posted: Thu Jul 02, 2015 6:12 pm
by Pablo César
Hola Luis,
Es posible disponibilizar un ejemplo con DBF y archivo con indices de la misma forma que utilizan ?
Los datos no precisan ser verdaderos, utilizá un replace secuencial para ejemplificar.
Seria bueno intentar entender lo que sucede y en la misma situacion que ustedes dicen.
Bueno tambien saber en que hardware y cual es el SO y version del HMG y modo (ANSI/UNICODE).
Re: REVISION OF GRID/BROWSE
Posted: Thu Jul 02, 2015 6:44 pm
by luisvasquezcl
Ok Pablo,
lo preparo y lo subo.
saludos cordiales,
Luis Vasquez
Re: REVISION OF GRID/BROWSE
Posted: Thu Jul 02, 2015 6:58 pm
by Rathinagiri
Luis Vasquez, the memory problem won't occur when we use virtual grid.
Re: REVISION OF GRID/BROWSE
Posted: Thu Jul 02, 2015 9:35 pm
by Amarante
Rathinagiri wrote:Luis Vasquez, the memory problem won't occur when we use virtual grid.
+1
Re: REVISION OF GRID/BROWSE
Posted: Fri Jul 03, 2015 4:10 am
by brain
tnx guys. is there a way to manipulate the database in minimal usage of array when using the grid/browse control. its hard to explain. i mean, if i want to show 1M records for 20 records per browse page. my arrays should to 20 only not 1M arrays. it is always everytime u down, up, pageup or pagedown your records only the record pointer is moving not the array.