Jump to content

Excel Report


---
 Share

Recommended Posts

Since we've upgraded to 7.2 we've been having issues with excel reports. If the report file is in.xlsm format we get the error "object variable or with block variable not set" when excel tries to generate the results. However if we save the report file as .xlt or .xls the excel file is generated just fine. So for instance if we use the canned Characteristic.xlt file everything works great. If I convert Characteristic.xlt to .xlsm we'll get the error. The only thing I can see that might be the issue is the .xlt and .xls are opened in compatibility mode in Excel and the .xlsm is not. So I'm guessing the compatibility mode might be executing the VB code differently than the normal/regular mode does. Or maybe our installation of Office is messed up.

Anyone else run across this issue?
Link to comment
Share on other sites

Yes,

I have customers that want the data exported into excel, so you have two options:

- A large dump of the PiWeb Reporting Plus database

- An excel export created for each measurement run - I just customize the report to add the Measurement Table as well as a button to perform the action.
Link to comment
Share on other sites

Well for one, I'm not using Pi Web for this part. But I tired this out just to see how it worked, and it's just a lot of extra steps. Even after you get the buttons set up you still have to save out every page and type a file name in. Its just way easier to just have the full sheet created in half a second and put in the results folder after the run is complete.
Link to comment
Share on other sites

Fair enough - yes for a single report it is extra steps.

Any reason you need each result in an individual Excel report? With the PiWeb Reporting Plus database you can export as much data as you'd like into one singular CSV that then can be easily parsed if needed.

I just ask these questions because I've never seen the appeal or need to use Excel exporting because it just creates one singular report for each part, so when needing to merge that data, there is a lot of extra work.

Either way, sorry to hijack your thread, hopefully someone who uses the native Excel export will chime in.
Link to comment
Share on other sites

Hi, I was trying a lot of methods for Excel reporting because for some reason we get error message each time we use excel report function in Calypso. I found out, that most comfortable for me is to switch on the Table file output and create merge file. Than a simple export from this merge to an Excel form for whitch I have a macro created. Full procedure is a matter of few seconds and its done.
Link to comment
Share on other sites

I don't use Basic PiWeb or have PiWeb Reporting Plus. I tried using Basic and Zeiss just makes simple things difficult. PiWeb is very pretty when I put time into the report. But if all I need is a point map I can take a screenshot in Calypso. There might be an easy way in PiWeb, I just haven't found it.

I use Excel and JMP to import the chr.txt files of individual programs. Takes under five minutes if it is a repeat job. With Excel I use Power Query to pull the data from a folder. Then a pivot table tab to parse the data. The customer form is on another tab and gets filled from the pivot table. JMP can import the data, then I can tabulate, add spec limits, analyze outliers, chart, etc.
Link to comment
Share on other sites

Please sign in to view this quote.

I'm interested in this to maybe try and link this to our CAQ.net system. I've also been having errors with excel. Are you taking the (3) table .txt files and merging them with this macro in excel? Trying to understand the process. Thanks!
Link to comment
Share on other sites

Please sign in to view this quote.

Hi Will,

no, I create merge file using Calypso directly (Resources -> Results to file... -> turn Merge on and press Initialization).
Measure the parts or recall them and then load the merge_chr file.

Hope this helps
Link to comment
Share on other sites

 Share

×
×
  • Create New...