TUniDBGrid

[dalpiaze]

It seems to be a problem with the component "TUniDBGrid", when using with DataSet "filtered".

 

When the DataSet it's non-filtered (full records), navigating around the records works well.

But when the dataset is filtered, the navigation loses control, selecting a prior record or jumping three records than the selecioned record.

 

This ocurrs when using UniDBGrid in "paged" mode and in normal mode too.

 

Any suggestions?

Thanks.

[chefdackel]

It is a known issue with some DBs, f.e. DBIsam and ElevateDB. Search through the forum to get some statements from the UniGui programmer what is the reason and what have to be done on his side to make this work.

 

In the meantime you can use some middleware like kbmMW or RemObjects. Using an additional tier also opens the world to an universal DB-access. But using f.e. DBIsam with a middletier server is far more complex than just only integrate DBIsam for data access, also because there is little or outdated documentation and not every middleware tool has such an excellent vendor based support like UniGui with this forum. If the middletier tool vendor does not provide free support based on a web forum, it is likely that you have to pay 150$ per hour to the vendor to get your questions answered.

[Farshad Mohajeri]

It seems to be a problem with the component "TUniDBGrid", when using with DataSet "filtered".

 

When the DataSet it's non-filtered (full records), navigating around the records works well.

But when the dataset is filtered, the navigation loses control, selecting a prior record or jumping three records than the selecioned record.

 

This ocurrs when using UniDBGrid in "paged" mode and in normal mode too.

 

Any suggestions?

Thanks.

 

I'm working on this issue.