Jump to content

UniDBVerticalGrid ERROR_2 in runtime show dataset


Ronbral

Recommended Posts

I will need to use a series of vertical grids with medical data in my project. The tables are generated at runtime, however I can not display the data in the Vertical Grid. In the example that follows, open the same dataset in a horizontal grid and in the vertical grid. Vertical does not display data, but ERRO_2 in all columns. I have already made numerous attempts based on the knowledge base of the Unigui forum, but I did not get any solution.

Please help me.

post-4420-0-29534300-1534713145_thumb.jpg

Link to comment
Share on other sites

 

I will need to use a series of vertical grids with medical data in my project. The tables are generated at runtime, however I can not display the data in the Vertical Grid. In the example that follows, open the same dataset in a horizontal grid and in the vertical grid. Vertical does not display data, but ERRO_2 in all columns. I have already made numerous attempts based on the knowledge base of the Unigui forum, but I did not get any solution.
Please help me.

 

 

 

 

Ha ha,I have met the same problem.ERRO_2.........,HOW TO RESOLVED THAT?DON'T FORGET TO TELL ME,THANKS.

Link to comment
Share on other sites

DD, following with the error investigation, I noticed that protecting the update from 

col ... findVirtualCol

 when 

gg.dbColumns is null

, "apparently" the functionality has been restored. Of course this is not a solution, as I could see other necessary care, and only a breakthrough in research; because this can help me meet the deadlines for a cursory presentation of what will be a future delivery ...

 

internalRender:

 

   if (vertGrid) {
      if (col.dataIndex != "l") {
          var _d = record.data._d;
          if (gg.dbColumns && gg.dbColumns.length>0) {
             col = findVirtualCol(gg.dbColumns, _d) }
        }
    }
Link to comment
Share on other sites

Following...

 

 

In my tests I validated

that in version 1.50.0.1475 the Vertical Grid applied to a run-time generated dataset mem presents the anomaly of not activating the EDIT when double clicking on a field. When compiled in trial version 1.10.0.1469, it works. This is true for the mem dataset ClientDataSet. KbmMemTable (what i use) does not activate the edit in either version. UniDBGrid works perfectly with both mem ds.

Link to comment
Share on other sites

  • 4 years later...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...