EPMsheet generation.

I have to generate report using 'WORKSHEET generation' and I am able to do it.
The sheet are generated for all entity under the selected parent.
When the sheets are generated the entity name is in the tab name of the sheet. However I need to name the tabs with format ENTITY_OWNER, than purely name the tab with 'ENTITY'name.
Each time I have 100 sheets and this has become requirement.
How to generate the sheets in this format...
Appreciate information on this...

Use VBA code to rename sheets after WORKSHEET generation. No other option.
Vadim

Similar Messages

Open vi error for report generation toolkt

Originally it works fine.
Now I upgrade to win7, LV9 and office2010.
To open the old program by 8.6.1, I reinstalled LV 8.6.1 and report generation toolkit.
But still got the error as attached.
Any suggestion, thanks.
Attachments:
ss.png ‏184 KB

1. MS Office 2010 is not yet supported, since it's still just a beta. I believe there are couple of changes that Microsoft make, and it could cause a problem.
2. LabVIEW 8.6.1, and all its toolkit is not supported on Windows 7. This could cause a problkem also.
In conclusion, you should use LabVIEW 2009, Report Generation Toolkit 2009, Windows 7, and downgrade office to XP, 2003 or 2007.
More information: http://digital.ni.com/public.nsf/allkb/C9408B9F08D711E786256F3300701D01

1st Generation iPod Touch No Longer Recognized by Windows 7 PC

I have a 1st generation iPod Touch (no camera) that can no longer connect to my Windows 7 pc. Plugging in the iPod via USB does not trigger any sort of dialog box in Windows and it doesn't trigger a message saying a device has been connected; the iPod does not show up in either iTunes, Computer, Device Manager or Devices and Printers, either as an Apple mobile device or an unrecognized device, and does not charge when connected to USB (though the wall-charger still works). As far as my computer is concerned this iPod does not exist. I had successfully synced this iPod as recently as one week ago and am ready to pitch the thing in the garbage if I can't find a solution.
I have the latest version of iTunes as well as the most up-to-date Windows updates. I have already followed all the steps listed here (iOS: Device not recognized in iTunes for Windows) multiple times with no success.
I also have tried following the instructions listed here (Re: For those Windows users who suddenly cannot see their device in iTunes. Here's a solution that has worked.) but this also hasn't worked since the iPod isn't recognized in the Device Manager and I am not given the option of updating the drivers, manually or otherwise.
I have uninstalled/re-installed iTunes and all related Apple services multiple times. The Apple Mobile Device Service is functioning normally. iTunes diagnostics indicate that there is no device connected no matter what I do. I have reinstalled my Windows USB drivers and changed the settings on the USB Root Hub in the Windows Device Manager to disable power saving options.
I have tried connecting the device to another PC which detects and syncs another apple device (iPhone 5) with no issues, and had the exact same result: the computer doesn't even recognize an iPod is connected.
I can't update the Apple Mobile Device Drivers because the device is not recognized by my machine in any way.
I even completely reset my iPod and that just left me with a unactivated iPod that still isn't detected.
I am really unbelievably fed-up with the useless "try checking your USB cable"-style advice that people seem to offer on this forum. If anybody has dealt with this issue and has any serious advice other than "re-install iTunes," it would be much appreciated.

You said "I am really unbelievably fed-up with the useless "try checking your USB cable"-style"
- Did you try another cable?
- Inspect the dock connector on the iPod for bent or missing contacts, foreign material, corroded contacts, broken, missing or cracked plastic.
Try on another computer

Issue with PTO (Paid Time Off) quota generation

Hi All,
We have an issue with quota generation of PTO for our employees.
The issue goes like this:
We have a Paid time off for employees 5weeks( 200 hrs) for employees who have worked less than 5 years.
we have paid time off for employees 6 weeks ( 240 hrs) for employees who have worked more than 5 years.
we have the following logic that has to go in this config:
-- Our fiscal year starts on Feb 1st and ends on Jan end or Feb starts which has a full week of working days. ( ex: if 01/31/2012 falls on a Thursday the following Monday which has full 5 day working week would be the end of the fiscal year).
-- Depending on the working hours of the employees and the date of joining for the first year ( for new hires)0041 info type the eligibility gets varied and reduced. Ex( employees who joins on start of fiscal year and works 40hrs per week schedules is eligible for 200hrs of PTO. Employees who join in the month of august and works for 35 hrs per week ( i.e mid of fiscal year) would get 91 hrs of PTO.
I need to put this in the system. I am thinking this could be done with out tweaking PCR.I need help in configuring this in Absence quotas as to what are the things i need change in system config and how do i do it. Please help with some screen shots if possible. I really need this to get it done ASAP. Looking forward for help.
Thanks,
Chowdary.

We use TM00 schema. Can i call TS15 and TS 12 rules into TM00 acheieve my issue of quota entilements?
Iam doing this because my businees needs to see if an employee chages his work schedule from 40 to 30 or 20 etc.. the PTO has to vary accordingly.
As the minimum eligibility is to work for 20 hrs to avail the PTO days. If at any point the employee drops it under 20 he will not be eligible till he work any this >= 20hrs per month so the evaluation has to check periodically to update the quota availability.... I need help plz suggest ...

I'm trying to get the ios 4.2.1 on my second generation iPod . Is there a way to install it directly on my iPod touch because my iTunes on my computer is not working. Please help Apple! I need the update. Just give me a link.

Im trying to get the ios 4.1.2 on my iPod touch 2nd generation. Can I install it directly on my iPod . My iTunes on my computer isn't working!

you have to have itunes installed but check out http://support.apple.com/kb/ht4623.

Report generation toolkit and signal express user step : problem of closing reference in "Stop" event

Hi all,
I'm trying to make a package of Vis to easily make Excel reports with Signal Express. I'm working on LabVIEW 8.2.1.
I'm using the report generation toolkit, so I build a .llb from my project which contains all the hierarchy of my steps, but also the hierarchy of dynamic VIs called.
I have made some steps, like "Open Workbook", "Write Data", etc.
My steps run well, excepts one step : "Close Workbook".
If my "Close Workbook" step is firing on "Run" Signal Express event, I have no error, so my reference is properly closed.
But if my "Close Workbook" step is firing on "Stop" Signal Express event, I have an error "1", from "Generate Report Objectrepository.vi".
I feel that I'm trying to use a reference which has been killed in the "Stop" step...
I would like to know what exactly do Signal Express on "Stop" event and why my close function does'nt run well.
Thanks,
Callahan

Hi Callahan,
SignalExpress (SE for short) does the following on the Stop event:
1. Takes the list of parameters that SE found on your VI's connector pane, and sets the values that the user set from the "Run LabVIEW VI" configuration page, if any.
2. Then tells the VI that SE is running the Stop event by setting the Enum found on your VI's front panel. This in turn should produce some boolean values telling your VI to execute the Stop case.
3. The VI is then run, with those values and states.
4. SE checks to see if any errors where returned.
5. Since this is the Stop event, SE releases the reference to the VI which it possesses.
Questions for you would be, is the reference to your Workbook linked to a control on your connector pane, or held in a uninitialized Shift Register. If it's held in a Shift Register, SE would not be aware of it, and would not be able to affect that reference.
Hope that helps. Feel free to post your LLB if it doesn't.
Phil

Report Generation: New Report.vi

Running applicaion in development mode works fine.
After compiling however I get Error 7: Open VI Reference in New Report.vi
Why am I getting this error?

Has the version of Office on your machine changed since you installed the Report Generation Toolkit? The VIs will become broken if the ActiveX interface changes, and this can happen when the Office version changes. I recommend uninstalling and reinstalling the toolkit. Also, what version of Report Generation Toolkit are you using? The latest version is 1.1.1.
-D
P.S. - I'm going to respond to your other thread that you started with a link to this one. Instead of creating multiple messages on the same question, just wait for a response to your initial thread.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Report Generation Toolkit Error (undefined erro)

Does anybody know what error -214 682 7864 (0x800A01A8) means when coming from the Report Generation Toolkit.
I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet. The error was generated all the way down in NIReportGenerationToolkit.lvlib:Excel_Get_range.vi (this is the ActiveX code).
Any ideas?
nrp
CLA

nrp wrote:
I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet.
Was it the first time you attempted to write the table to that spreadsheet?
Maybe the error is due to the spreadsheet grown oversize than its limit so that it cant accomodate the table anymore.
What is the version of MS Office you are using? I think Office 2003 can go only upto 1024 columns...
- Partha
LabVIEW - Wires that catch bugs!

Report Generation Exe Error

Hello,
I am using LV 8.6.1 with the 1.13 report generation toolkit and I am having problems getting my built exe to work. I am trying to open an excel template and populate it with new data. I have broke the vi down to just opening excel - opening the template and then fill in some data. But at this point excel does not open at all. And naturally everything works fine in the development environment.
Error Code: -2147352573
Member not found in NI_ReportgenerationToolkit.lvlib:
Excel_open_workbook.vi
NI_Excel.lvclass: new reportsubvi.vi
I read a few help pages that said to add \vi.lib\utility\NIreport.llb and LVclass directories to the project folder and add them to the always include section of the build. But no luck so far.
Side question: The machine I want to use this on has 8.6.1 Full which does not have the extra excel functions that my developer has. Is there a way to install the DEV report generation toolkit in the full version? Then I would not need to build an exe.
UPDATE: I just tried the exe on a different machine that has a developer suite installed and it worked fine. So I guess I need to find out what else I need to add to the build to make it work.
Message Edited by _Bryan on 06-16-2010 11:58 AM
Solved!
Go to Solution.

There should be some info on this in the KB.
But first you should make sure that your version of the report generation toolkit actually supports excel 2000 (which is 10 years old)
That should be in the release notes of the toolkit
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Report-generation vi problem

On a Windows XP system using the "Text Report Example" vi, the (read) report property node item "TextFont" (stdole.Font) at the beginning of the "Font Style" vi which is a part of the "Set Report Font" vi is returning this error:
"-1073741819 Unknown System Error in Font Style.vi->Set Report Font.vi->Easy Text Report.vi"
Any suggestions as to a cause and cure?

This Knowledge Base from NI's website actually deals with this problem. The fix depends upon whether or not you have the Report Generation Toolkit for LabVIEW. There are fixes for whether or not you have the Toolkit. Hope this helps.
J.R. Allen

Report Generation for Excel does not work after using the Application Builder

I have a VI that writes data to an Excel file using the Report Generation Toolkit. I recently compiled the VI into a single Application (EXE) using the Application Builder. My VI runs its tests properly, but no data is written to Excel. What could be the cause? I don't receive any error messages.

Hi
I usually build exe-files, which sometimes also have report functionality.
Open the Application Builder and check the following things:
1. Add the following vis: _Word Dynamic VIs.vi, _Excel Dynamic VIs.vi They should be located in the directory ..\LabVIEW X.X\vi.lib\addons\_office in the llbs _wordsub.llb and _exclsub.llb (report1.jpg)
2. If you use an Installer, go to the Advanced Settings. There you can select some things to include in the Installer. Check if "NI Reports Support" is selected. (report2.jpg)
These are the things I always do, if I need reports and I never had problems up to now. I made two screen-shots of these settings.
Hope this helps.
Thomas
Using LV8.0
Don't be afraid to rate a good answer...
Attachments:
report.zip ‏25 KB

Report Generation Toolkit producing error -2147417842, "The application called an interface that was marshalled for a different thread."

Hi everybody,
I've got an application that logs data to an Excel spreadsheet using the Report Generation Toolkit. My VI's have worked fine in the past using Excel XP, but since I've upgraded to Excel 2007, I am getting COM errors like this one:
"Error -2147417842 occurred at The application called an interface that was marshalled for a different thread. in Excel_Insert_Text.vi" That is the exact wording, even with the weird punctuation and capitalization.
The first occurrence of the error is not determinate. Sometimes, up to 10 logging sessions, involving a new .xls file, can occur before this error pops up. Once this error occurs, I must quit LabVIEW to resolve it. If I try to do anything with Excel, I always get this error, although sometimes it comes out of different source VIs. Excel_Open.vi is another.
These logging VIs have worked just fine until upgrading to Excel 2007. I checked, and I was using a really old version of the Report Generation Toolkit, v1.0.1. I read the documentation and had a big sigh of relief when I realized I needed to upgraded to v1.1.2 to get Excel 2007 support. However, even after upgrading, I'm still getting the same errors. I'm using LabVIEW 8.0.1, and I'm also building these VIs into an application. The error occurs both in the LabVIEW IDE and in the built application. Does anybody out there have any idea what I can do to fix this? I googled a little, and discovered this is a COM error, but I can't find any references to the Report Generation Toolkit specifically.
Thanks,
Phil
Solved!
Go to Solution.

Hi Christian,
I do not see that exact option listed, do you mean "user interface"? I recognize the "Run in UI Thread" option, it's on the Call Library Function Node.
I checked, and my top-level VI has "same as caller" set, and I believe all my VIs are set to "same as caller". Are you suggesting I change my top-level VI preferred execution environment to "user interface", or just the logging sub-VIs that use the Report Generation Toolkit?
Thanks,
Phil
Attachments:
VI_properties.png ‏15 KB

Report generation for FPGA VI

Hello..
I want to include the number of resources used by FPGA (LUTs, slices, blockrams etc) in my report generation.
After compilation is completed, a window showing these resources will occur. But, how can I add this compilation report in my report generation...
Please let me know..
Thanks
Prashanth
Solved!
Go to Solution.

Hi
I made a small code which helps you achieve this functionality.
Hope it helps!
In this code: I read from "toplevel_gen_xst.log" file generated for the project; search for the string "Device utilization summary" and extract the part of interest Now you add this extract to your report compiled using report generation toolkit.
regards,
Ravi.
Attachments:
image.jpg ‏60 KB
FPGA Utilization.vi ‏10 KB

Report generation toolkit VI error when running EXE

A VI inside the Report Generation Toolkit (version 1.1.2), Excel Find Application Directory.vi, will not function correctly when running an EXE. The "Current VI's path" block will return the path of the currently running EXE rather than the path of the Excel Find Application Directory VI. (The same would be true for Word Find Application Directory.vi.)
-Joel
Solved!
Go to Solution.

Have you had a look at this knowledgebase article? The error is caused due to the exclusion of any dynamic VI.
Ipshita C.
National Instruments
Applications Engineer

LabView Exe Application file not launch Excel application for report generation

Dear All,
I created one LabVIEW application file for report generation (using Excel Template).
While I run the program in programming mode it works well and create the report file in the specified path.
After creation of the application file(exe), it gives the correct path of where the excel template is placed. The same path is given to New Report.vi, but it gives the error 'File Not Found'.
Tell me, is any other configuration required for generating Excel reports? (During exe application mode)
Give me the solution.
Thank You
Jegan.

Hello,
Most likely you are encountering a problem of stripping and/or building paths. Probably the easiest thing to do is put a couple indicators on your front panel for the path or paths you care about, build your exe, and make sure you are really using the path you'd like. If you always put the report at some deterministic place relative to the exe (that is, even it the exe is moved, it will go with the exe and remain in the same relative path location, then you can use the Current VIs Path funtion found in the ... File I/O -> File Constants palette as a start path (where you will want to strip at least the exe name off of course).
I think this will bring some clarity to the issue!
Best Regards,
JLS
Best,
JLS
Sixclear

EPMsheet generation.

Similar Messages

Maybe you are looking for