more quick actions
minimize quick actions
Topic starter
Hello,
I had a customer project that triggers a windows batch script to trigger database replication. The batch script is triggered from Scada Basic instruction SYSTEM, mode SYSTEM.
The batch script command window should be appearing only for a brief moment. But whenever the user is working on the station, and the CMD window appears, if he accidentally clicks on the CMD window, it will be frozen, and eventually, PcVue is frozen.
So I checked and found some information, so I write this topic for sharing.
Normally when a batch script is running, and you click on the window, it will continue running as normal. But in some cases, it will pause the script. It is explained in this superuser topic.
So how to avoid the batch script from pausing on click, you may open the CMD property and disable "Quick Edit Mode". By doing this, the CMD window is no longer paused on click.
Posted : 12/08/2021 2:42 pm
Hello Kantha
Don't use Scada Basic instruction SYSTEM, mode SYSTEM to trigger a replication..I did it a long time ago with PcVue 8.1...when there is no or few data to replicate it's OK but when the database size will increase (and replication become longer)it will not work anymore. Sacada Basic instruction SYSTEM waits the end of the process you call..
Scada basic instruction Application, mode LOAD is a better solution because it executes the replication but without waiting its end.
Posted : 08/09/2021 4:53 pm
And I add 1 point which is only related to the previous remark
If you are NOT using SQL Express -> Use the SQL Server built-in replication feature 😉
Nico
Posted : 08/09/2021 4:58 pm