Your Products have been synced, click here to refresh
The error is generated by DPUPDATE.EXE when it detects an invald database path. When any error occurs, the XSTATS11.TMP file is not deleted.
Since DPUDAPTE requires the XSTATS11.TMP file to be in the same directory as it is, I think pcmdis now copies DPUPDATE.EXE and other files to the user app directory (windows compliant issues) and is executed from there. So you may have 2 copies of DPUPDATE.EXE under the same version of pcdmis to deal with. If you delete the DPUDAPTE's, I would imagine pcdmis would then generate a message about it not being there. Not sure what you did in prior versions with DPUPDATE. Did you replace it with your own app?
The error is generated by DPUPDATE.EXE when it detects an invald database path. When any error occurs, the XSTATS11.TMP file is not deleted.
Since DPUDAPTE requires the XSTATS11.TMP file to be in the same directory as it is, I think pcmdis now copies DPUPDATE.EXE and other files to the user app directory (windows compliant issues) and is executed from there. So you may have 2 copies of DPUPDATE.EXE under the same version of pcdmis to deal with. If you delete the DPUDAPTE's, I would imagine pcdmis would then generate a message about it not being there. Not sure what you did in prior versions with DPUPDATE. Did you replace it with your own app?
© 2024 Hexagon AB and/or its subsidiaries. | Privacy Policy | Cloud Services Agreement |