On 30.03.2017 12:50, Matthias Schäfer wrote:
> Dear Mr. Kueng,
>
>
>
> thanks for your quick reply. I have further information for you:
>
>
>
> The Script is perfectly working with 1.7x version. Updated to 1.9.x
> SubWCRevCOM.exe causes the “error”:
>
> · Excel freezing
>
> · SubWCRevCOM.exe consuming 12 to 13 % CPU Power constantly
>
> · SubWCRevCOM.exe memory grows and grows … up to 1.3 Gigabytes
> (then I stopped the process, otherwise it would grow further and bigger).
>
> I made an error handling for the complete script, so it is ensured that
> the VBA Code is not causing the problem (Please remember that its
> working fine for years now with V1.7x).
>
> Because there is no documentation for VBA (except some snippets from
> internet and sourcecode etc.) I was not able to find out how to check
> out the result out of “oSvn.GetWCInfo ActiveWorkbook.FullName, 1, 1”. Do
> you have an idea how it has to look like in VBA?
>
>
>
> There are two instances to control the errors:
>
>
>
> · “On Error GoTo NoSVN” (to the end of script) --> for the whole
> script (if there is any error the whole script is stopped!)
>
> · “If oSvn.IsSvnItem = True Then” --> The second instance, that
> checks if the file is in SVN-control. (If the data is no SVN-Item the
> script stops, too)
>
> o Even if the file has no SVN-Control the SubWCRecCom.exe is opened
> and seems to struggle. That must have something to do with this code:
>
>
>
> I reckon, that when the object is created in VBA with this command, the
> SubWCRec.exe is started. Then there is an not identified error, but the
> SubWCRev still runs with memory overflow without being stopped. Excel is
> working after killing the process SubWCRev manually.
>
>
>
> Something must be changed, because if I replace the SubWCRevCOM.exe to
> Version 1.7x it is working great. Rest of files in this case are still
> on 1.9.5.
If you replace SubWCRevCOM with an older version and it works without
having you to check out a new working copy, then of course the new
SubWCRevCOM won't work: the working copy formats are not compatible.
You have to run a WC-Upgrade on the working copy first:
with TortoiseSVN, right-click on the working copy root folder and then
select "Upgrade WC".
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3225155
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2017-04-01 03:14:10 CEST