Editor 8 prompt: "The procedure you are about to open already exists in *.mc format:"
If you are using MET/CAL Editor 8.0 or newer to open existing compiled procedures inside of a proc.dir, you may have already seen this prompt:
The first time you open a procedure from a proc.dir, the Editor automatically creates a subdirectory to that proc.dir called MCFiles. The Editor also saves your newly opened procedure as a file within that directory, and names the file after the first instrument line of the procedure. For example:
The original proc.dir resides at: ........................... M:\production\proc.dir Opening a procedure from this proc.dir automatically creates: M:\production\MCFiles\ The procedure is auto-saved to: ............................. M:\production\MCFiles\Sub Copyright.mc
Any changes made to the procedure are then saved only to this new *.mc file. The changes do not become available to Run-Time until the procedure is Published back to the proc.dir, using Build > Publish Selected Procedures (or when a package is created, but that is another topic). This allows the procedure developer to work on this file, or multiple files, as long as they need until finished, saving their progress along the way. None of the changes become "live" until they are Published back to the proc.dir. You can elect to use the *.mc files as your procedure source, or continue using the proc.dir as the procedure source; the decision is up to the procedure developer.
This behavior may be very similar to the operation that many procedure writers performed in MET/CAL 7.3 and earlier, where they had a production copy of proc.dir. They would then copy any procedures that required editing to a development proc.dir, make and test their changes, then copy them back to the production proc.dir. Now, instead of using a development proc.dir, you have *.mc files inside of the MCFiles directory.
With all of that said, if the developer elects to use a proc.dir as their procedure source, this means that each time a procedure change needs to be made, the procedure will be opened from the proc.dir. The Editor will recognize that a *.mc file was already created as described above. The message in the attached image is asking you to confirm that you want to open the contents of compiled procedure from proc.dir, replacing the existing *.mc file. This is also why it gives you the date and time information for both the compiled proc and the *.mc, this is the Editor’s way of helping you ensure that you open the correct procedure and not accidently over-write something that you may have worked on previously.
If you instead elect to use the *.mc file as the source, then you will just open existing text files, make your changes, then Publish them; you will no longer re-open procedures from the proc.dir unless you want to overwrite the contents of a particular *.mc file.
Please sign in to leave a comment.