We're having an esoteric issue with custom tool palletes. Our company has several custom tool palettes that are called by custom toolbar functions in cad. They've all worked fine until we installed C3D 2023, but now one doesn't work in any version of CAD installed. Each custom tool palette macro points to a different folder on the user's C drive. A script copies these files from the server at each logon to Windows. One of the tool palette options has been having an issue where the *.atc files are deleting the data contained within after the CAD macro call. This doesn't make any sense because the CAD custom function is straight forward and doesn't include anything that would alter native files. (^C^C*_Toolpalettepath;C:/CADSupport/Toolpalettes/Deploy/2;TTP;).
We will then manually copy the *.atc files from the server to the user's C drive. Each file will be dozens of kilobytes. Then we run the script in CAD to point to the subject tool palette. Only a fraction of the palette tabs will work, if any at all. We then check the files in the user's C drive and several, if not all, of the *.atc files have been reduced to 1kb and do not contain the necessary information. This can happen even if the *.atc files are set to read only.
The weird thing is that if we repeat this process five or six times, manually copying the *.atc files from the server to the local machine and then calling the CAD function, eventually it all works and the *.atc files all contain the correct information.
Anyone aware enough of CAD interal code to venture a guess as to why these files would be reset after a simple call from CAD? Telling users to try copying files five or six times just seems unprofessional. Is there a reason there would be a problem with leaving CAD open while we overwrite the local versions of the *.atc file? Often, our users don't recognize there's an issue until CAD is open but maybe we need to be checking every morning?
