|
| Iniciado por guest, 06,jun. 2017 08:20 - 4 respuestas |
| |
| | | |
|
| |
| Publicado el 06,junio 2017 - 08:20 |
Hi all
We have a situation where the 'data history function' works perfect and one client whose history does not always work as it should.
So we decided to implement our own history files.
I am sure someone already did this.
Would whoever did this, please give us some hints as to were to hook our code so it has the least impact on the software and any other hints that you deem you can share.
Thank you very much
Noel |
| |
| |
| | | |
|
| | |
| |
| Publicado el 06,junio 2017 - 13:25 |
Hi Noel
if you are talking about hat I think, you have a full example of that in WXReplication:
- I have created global procedures hadd, hmodify, and hdelete overwriting the regula ones
- in them, I'm writing the data changes in my replication file (before transport) THEN doing the real hxxx function
Now, in Wreplication, this is not done in order to verify the history of the data changes, but to SEND the information to another computer. However, the system works fine this way and you could easily write a "history viewer" just reading the wxreplication file.
The best part, of course, is that is you remove all the stuff specific to the replication, you can implement that without any change in your code (if you are not doing update queries, that is).
Best regards |
| |
| |
| | | |
|
| | |
| |
| Publicado el 06,junio 2017 - 13:31 |
| |
| |
| | | |
|
| | |
| |
| Publicado el 06,junio 2017 - 14:11 |
Hi Fabrice
Thanks
I will have a look at the WXReplication.
Regards
Noel |
| |
| |
| | | |
|
| | |
| |
| Publicado el 07,junio 2017 - 08:24 |
Hi Darren
I will look at wxreplication first as there seems to be a compete setup.
If it is too complicated for me  then I will need a way to find which data has changed and setup the triggers.
Thanks for you help.
Regards
Noel |
| |
| |
| | | |
|
| | | | |
| | |
|