The problem here is that every time we update a section view we are writing the hatch data to the pfm file drafting keeps and we don't delete it. After a lot of update operation the pfm file grows until the upper limit of entities.
This file is not corrupted and the user can save it. He needs to find the name of the pfm file in the data directory ( you can see the path of the file in the DM browser and the name if the exl file will be also the name of the pfm file). The next phase is to copy the file standard.pfm from cimatronE/cimE/it/dat/defdata directory and change the name to the name of the original pfm file.
With these operations we replaced the original pfm file with the standard pfm file. You don't need to worry about the data in the pfm file. We are using the pfm file only for users that have old IT frames (and we have some).
After the change the user will be able to open the file and update it. 作者: sunnymmyg 时间: 2005-6-28 17:15
用哪个指令组合起来？