Recent content by aluck

  1. A

    RecNo doesn't work properly when used within OnCalcFields

    It's ok, but I do not understand if service contract matters in such a case.
  2. A

    RecNo doesn't work properly when used within OnCalcFields

    I have a service contract with Allround Automations. Does it mean that I should expect to get patches a bit early than a month after bug report? ------------------
  3. A

    RecNo doesn't work properly when used within OnCalcFields

    Thank you. I'm looking forward for the responce.
  4. A

    RecNo doesn't work properly when used within OnCalcFields

    First, I think that RecNo is the only 'legal' way to obtain additional 'No' column in a grid. TTable, TQuery, TRxMemoryData, TFIBDataSet (Free InterBase Components) works in such a way, and all they allow to get .RecNo value in an OnCalcField event handler. Second, there IS a bug in...
  5. A

    RecNo doesn't work properly when used within OnCalcFields

    Sure you are. First, there are many RDBMS that doesn't support ROWNUM feature. Second, in such a case there is NO way to show record number for ordered data. If I ever need just a kind of record identifier it definitely would be a primary key.
  6. A

    RecNo doesn't work properly when used within OnCalcFields

    Certainly. PL/SQL User's Guide and Reference Release 8.1.6 Part Number A77069-01 "ROWNUM returns a number indicating the order in which a row was selected from a table. The first row selected has a ROWNUM of 1, the second row has a ROWNUM of 2, and so on. If a SELECT statement includes an...
  7. A

    RecNo doesn't work properly when used within OnCalcFields

    It seems that TOracleDataSet.RecNo works incorrectly in some situations. I have a calculated field (say, 'RecNo') and OnCalcFields event handler like: OracleDataSet.FieldByName('RecNo').AsInteger := OracleDataSet.RecNo; Right after dataset opening the RecNo field in TDBGrid looks like a...
See more
Back
Top