Hello,
I use DevExpress VCL components and some of them have both append and insert like quantumgrid (cxgrid). Unidac dont have any afterappend event so i cant catch when the user appends, only inserts. Can You add an after append event?
Append event needed
Re: Append event needed
OnAfterInsert event of DatasetCmp or in DataSource events
if you dont COMMIT you have one Append post
if you dont COMMIT you have one Append post
Re: Append event needed
Nope, OnAfterInsert wont fire on CXgrid append, but it will fire on a CXgrid insert. No event in tUniQuery will fire after an CxGridAppend. That is the problem.emailx45 wrote:OnAfterInsert event of DatasetCmp or in DataSource events
if you dont COMMIT you have one Append post
Re: Append event needed
The dataset OnAfterInsert event should occur when inserting a record and appending it. More about this in the Embarcadero documentation: http://docwiki.embarcadero.com/Librarie ... fterInsert
The described problem is not reproduced when using standard TDBGrid. Please address this question to the DevExpress developers.
The described problem is not reproduced when using standard TDBGrid. Please address this question to the DevExpress developers.
Re: Append event needed
Hello,
What I can see in DevExpree help, there is something missing in the data-source (in this case the tUniQuery).
https://www.devexpress.com/Support/Cent ... ls/Q242068
Regards, Pär
What I can see in DevExpree help, there is something missing in the data-source (in this case the tUniQuery).
https://www.devexpress.com/Support/Cent ... ls/Q242068
Regards, Pär
Re: Append event needed
Try to reproduce the problem you’ve described using TDBGrid. If the problem is reproduced, then send us a small test project via the contact form on our website: http://www.devart.com/company/contactform.html . Please also include scripts for creating test tables in the project.
If the problem is reproduced only on DevExpress components, then contact the developers of DevExpress to solve the problem.
If the problem is reproduced only on DevExpress components, then contact the developers of DevExpress to solve the problem.