Code: Select all
tStart = NOW; #... # Do something in other process code #... tEnd = NOW; RunProcess('ProcessCaptureStats', 'pnStart', tStart, 'pnEnd', tEnd); # OR RunProcess('ProcessCaptureStats', 'pnStart', tStart, 'pnEnd', NOW);
Now, this is easy enough to work around; just wondered if anyone else has seen this or similar issues with other functions and RunProcess. We have not seen any other parameter processing issues, but have only tested RAND. We also tested multiplying NOW by one which led to a time about 1.5 hours in the future. Multiplying NOW by two resulted in the process reporting that it completed about 20 years ago. So, armed with this knowledge, we can provide finance departments with the ability to complete their work years ago.
We did a good bit of testing. For now, just going to convert the NOW results to a string and pass that to the sub.