Basic Script for Execution

Hello & welcome!

Let me try and get a better understanding of what you're looking to accomplish - you have a lot of programs, and a lot of machines in different configurations. You want to be able to run a program, and export the report to Excel, using a custom template. Is this correct?

I am curious why you would not want to use Excel on the machine - without it, you only have access to the PDF version on the machine, and any Excel reports would have to be viewed from a different computer, correct?

You currently have a script that exports dimensions to an Excel file? Without Excel? Or is all your data already located (somewhere) and you're trying to pull it into a different location, in an Excel file?

I created a template within the Excel Form Reports that will work on the machines to create the excel file without having excel on the actual machine itself.  I know I can accomplish this but the Excel Form Reports is based on execution not the report window, so when I have an operator (button pusher with absolutely no experience within DMIS) that needs to go back and run a hole because they messed their hits up.  I am an offline programmer working in the office not on the floor so I try to automate anything and everything.  The operators just look at the report window within DMIS itself for review.  My current script will work if I put Excel on each of the machines, I am just being stubborn at this point because I know this can be done without investing in excel.  Our current process is the datapage executable at the end of each program.  On a full execution it automatically generates an XML for the database at at the end of execution.  If they ran something backwards or took a wrong hole they can go back and execute each feature as needed.  They then review the report to make sure there is no more operator errors,  view full report mode, and they can run the executable as a block to generate and additional full report with no errors.  My thinking is if I can create a script that just executes all dimensions (not features themselves)  and place it at the end of the program just before the excel form report command.  Each time I would need to provide a full report, the operator can just execute the script and excel form report together.  I was having trouble 

I see! I had a similar setup some time ago. What I ended up doing to accomplish this was setting up a custom form at the beginning of each run. As a standard machine shop running valve spools (cylindrical parts with several round or flat slots and cross holes), we had Blanking, Milling, Rough Grind, Plate, and Finish Grind operations that would happen on each part. Five or ten blanks could make several hundred different pieces, so it was easier to program the CMM to run a family of parts within a single program, rather than each individual part number having a separate program. This made editing a routine significantly easier, since the logic should follow across the board for similar parts.

When the operator would hit Execute, a form with several options would come up first. There were several radio buttons that would determine the operation as listed above, and some check boxes that would allow for different reports to be generated from the same program. One of the operations was simply "Print Report", which would only execute the report generation section of the program, which I always located at the end of each program. Each section was a different GOTO command; <code>If [This Box Checked], GOTO [Print Report]</code>

I generated a Youtube video on how to generate a Form that will allow that - check this link for the video.

Essentially what this is doing is selecting different start points for the program. If the program "starts" at the beginning of the report, it will simply pull all of the already-generated results into the report, in whatever format you have programmed in there. The operator can do this manually, but it can be difficult to get them to understand exactly where to run from.

TLDR; I used a Custom Form and special programming techniques to accomplish this. As far as an external script to do the same thing, another will have to chime in

TLDR; I used a Custom Form and special programming techniques to accomplish this. As far as an external script to do the same thing, another will have to chime in