Excel toolkit --excel save.vi is broken arrow

After installing the Goop toolkit and excel toolkit . I found that the "excel save.vi" having broken arrow and give me an error.
Attachments:
save_as.jpg ‏31 KB

Ok, first -- do you have excel installed? Sorry, had to ask.
It seems a little odd that you say the vi has a broken arrow and also gives
you an error message. Does that mean that the vi will try to run even
though it has a broken arrow but then it gives an error message, or do you
mean that even without running it it gives an error message?
I once had a vi with a broken arrow but no error in the error list window.
I clicked the box to show warnings and it turned out that it was a warning
that caused the broken arrow.
"YCHENG" wrote in message
news:[email protected]..
> After installing the Goop toolkit and excel toolkit . I found that the
> "excel save.vi" having broken arrow and give me an error.

Similar Messages

Report Generation Toolkit 1.01 and broken arrow

Hi,
I desperately need help because I need to build my application tomorrow morning for our production department and have trouble with the report toolkit.
I am aware of your knowledge base entry regarding this problem. I already deinstalled and reinstalled the toolkit (version 1.0.1 for LV 6), and I checked the windows registry entries. Still, after mass-compile, the report generation toolkit VIs are not executable (broken arrow, invalid property node). I have LabVIEW 6.02, 7.0 and 7.1 on my computer and I am using the report generation toolkit version 1.0.1 with LabVIEW 6.02 and version 1.1 with LabVIEW 7.1. The application that I need to build is written in LabVIEW 6.02. What else can I do to get rid of the broken arro
ws?
Thanks in advance for your fast answer....
Gabs

Hi,
the problem is the following: during the build error 1003 occures at ....\internal.llb\Word_New_Page.vi. Possible Reasons: LabVIEW: The VI is not executable. When I open my main VI, I see no broken arrow. When I force a mass-compile (Strg+Shift+Run button), the broken arrow appears suddenly. I can then see the following error message: Word Easy Text.vi is broken because Word Format Text.vi is broken because the Property Node Range\Style calls an invalid property. Actually, the property nodes in these VIs have NO properties and the invoke nodes NO methods.
I know now that this is due to the fact that I need to build this application for a computer on which Word97 is running, so I installed the Report Generation Toolkit for Word97. But - on my developme
nt computer where LabVIEW is installed Office XP is running, not Office97. If I install the Report Generation Toolkit for OfficeXP, no error occurs during the build, but the executable does not run properly on the target computer (when calling Word97).
Question for NI: How am I supposed to build an executable using Microsoft Word Report Generation Functions if the target computer has Word97 installed but the development computer has WordXP installed???
Please help,
thanks,
Gabs

MS Office Report (Report Generation toolkit) is not executable, Xnode broken?

Hi, I am trying to generate an excel report, and I figured it would be easier to use the MS Office report VI, but I am getting the broken arrow saying the SubVI is not executable and that the library that defines the xnode is broken... here is a screensot attached, I already uninstall and reinstall the report generation toolkit and still the same... this is what I found on NI: "This error occurs when the library that defines the XNode you used is broken. To correct this error, reconfigure the XNode." but no idea how to reconfigure xnode
Attachments:
Error.png ‏67 KB

What version of LabVIEW are you using?
What is the nature of your Report? What should it look like? What kind of data should it contain?
Can you show us some code that you've tried to use? If so, include the code as either a Snippet or as a VI attachment (so we can plug it into our own LabVIEW installations and experiment with it).
I generally find that the Report Generation Toolkit is a very easy way to generate Excel Workbooks. I work primarily with LabVIEW 2012 and LabVIEW 2014.
Bob Schor

Labview crashes every time I click on a broken arrow (vi has errors).

I just upgraded Labview from 7 to 8.5.1 a few weeks ago. Now, when I press the broken arrow to check the errors in a vi, Labview crashes. This is a vi that was developed using the state diagram toolbox under Labview 7. I now have the state chart toolbox but not the state diagram toolbox.

Try to disconnect the state diagram from the the state diagram (right-click on the main while loop).
If that doesn't work in 8.5, try to do this in 7.1.
Or install the state diagram toolkit in 8.5.
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!

Why a VI has a broken arrow when I open it when labview is open but becomes executable when it is opened by double clicking

I have a VI with some subVIs from a dynamic link library. When I open the VI using "open" or "open VI" in labVIEW, the VI is broken. In the error list,it saids one or all the subVIs from the dynamic link library are not executable. However, if I exit labview and open the same VI by double clicking it, it becomes executable without any change being made. Sometimes I can fix the broken arrow by configuring the "call library function node" in the subVI and saving it. But when I open the VI again, the same problem and error message appear. I am using labVIEW 6.1 for the top level VI and those subVIs from the dynamic link library could be developed in a different version of labVIEW. Is this the cause of the problem? Another possible reason I can think of is that somebody installed another application developed in labVIEW on the same computer. Is it possible that some settings were modified during the installation that cause this problem to occur? I am suspecting this because I first notice this problem after the installation of the other application.

Since the problem started ocurring after installing another application, I would suspect something with that last installation. Without knowing more about the installations, I would not be able to help much. Did the other installation perhaps install another DLL of the same name? Try uninstalling the last app to see if the problem goes away.
- tbob
Inventor of the WORM Global

Broken arrow but no errors?

I have a VI that has a broken run arrow but displays no errors when I
clicked the broken arrow. I can find no obvious errors on the diagram.
It was working fine and then I added another control to a cluster and it
started giving me the broken arrow. I removed the new control and I
still get the broken arrow.
Any help? I'm using LabVIEW 6.0i on Windows 98.
-Stephen

Unfortunately, it is possible for some node or control to break a VI,
but when
asked to elaborate, it doesn't give any reason. This is a bug,
hopefully one
that is fixed in the latest patch, but if not, it needs to be investigates.
You might want to upgrade to 6.02 first. If that doesn't fix it, you should
send the VI to NI technical support so that the bug can be investigated.
Greg McKaskle
>
> Thanks for the reply. I have tried Cntrl-B, forcing a recompile, saving
> under a different name. None of these has worked.
>
> -Stephen
>
> Johannes Niess wrote:
> >
> > Stephen writes:
> >
> > > I have a VI that has a broken run arrow but displays no errors when I
> > > clicked the broken arrow. I can find no obvious errors on t
he diagram.
> > > It was working fine and then I added another control to a cluster and it
> > > started giving me the broken arrow. I removed the new control and I
> > > still get the broken arrow.
> > >
> > > Any help? I'm using LabVIEW 6.0i on Windows 98.
> > >
> > > -Stephen
> >
> > Ctrl-B

PSE7 saves edit as broken file

I have been using PSE7 for a few months. It went through a period where it wouldn't edit at all. Then it starting working. Now for the past week it will edit but it saves as a broken file. Can anyone help? I am running Windows XP and have not made any changes to my computer recently. I also have PSE3 and it won't edit either. I get the message "Adobe Photoshop 8 does not run under this version of the operating system. Please check the package minimum requirements for the operatins system lever necessary for this software". It had worked fine for three plus years, now this. Thank you.

There could be a lot of reasons for a broken thumbnail.
One suggestion is for you to check to make sure you are saving the file with a valid extension in the file name ... something like .jpg or .psd or .tif would be examples of valid extensions (of course, there are others). If the file name has an invalid extension, then you might get a broken thumbnail.
Another possible reason for this is that you have used two periods in the file name. Something like Boston.May2009.jpg is invalid.

Broken Arrow with Case Structure Input Selector

Generally We get a broken arrow when a case structure
is wired incorrectly to its case selector .
I found that even after this is fixed, the arrow remains broken.
however when you click on the broken arrow, the VI
starts to execute instead of highlighting the error.
Seems like a compiler Issue.
I want to know if anyone has faced this issue.
I am currently using LV 8.6
Regards,
Sundar.

SUNDAR.N wrote:
Generally We get a broken arrow when a case structure
is wired incorrectly to its case selector .
I found that even after this is fixed, the arrow remains broken.
however when you click on the broken arrow, the VI
starts to execute instead of highlighting the error.
Seems like a compiler Issue.
I want to know if anyone has faced this issue.
I am currently using LV 8.6
Regards,
Sundar.
I can confirm that. I HAve seen it with type defs as well as LVOOP classes.
I have never been able to reproduce it on demand but it always seesm to be associated with situations where a type or class definition was changed. I think I have seen this issue on and off from LV 8.2 thru LV 8.6.
Ben
Message Edited by Ben on 07-31-2009 06:59 AM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Broken Arrow makes LV crash !!

Hi,
A while ago I excperienced a problem with activation of the broken arrow that made LV to crash.
By simple activating the same functionality by using the menu selection "View->Error List"
I found a work-around that worked fine, for a while.
Now I back to square 1. I can not develop my code anymore.
No help seems to be found.
Does anyone have any idea what to do ?
Regards,
Mikael Ekman

Hi GerdW,
The problem is that there is no (visible) errors in the code.
Without errors it is OK to run the and the arrow is solid.
If I disconnect a wire the broken arrow appear, as it should.
If I activated the LV crashes. That problem make development a hell.
The code is big. Top VI about 3.5 Mb using roughly 50 sub VI.
There has to be a built in problem in the LV.
This problem suddenly appeared after upgrading to LV 8.2.
Regards,
Mikael Ekman

Excel save

I have an application with a lot of excel functions going on using ActiveX. When I create a line to be added to the excel file it stays in memory but is not written immediately. When the LV app closes and uses close /save the file is written. I want to save each addition in the files in case the program crashes and does not exit gracefully. So that no data is lost.
Here is my function that adds each update to the excel file.
I thought the last activeX function would save the file each time I add something to the workbook.
It needs to update automatically without operator intervention.
Can someone tell me what I have wrong?
Thanks
Judd
Judd
Attachments:
temp excel write string.vi ‏24 KB

Dear Judd,
You are using the correct function/method for save (Excel Workbook - Save).
Probably you check,
1. The sequence of the functions you are using
2. Error conditions,
3. Write Permission of the file
4. Write Protection/Properties of the Excel Cells
5. The Range you are using (Range of Cells)
Also I am suggesting to save the file before closing it (PFA).
Note that while debugging you can launch Excel Application with 'Visible' and put breakpoint before closing the excel file/or where you want.
So that you can cross-check that the write function is working properly.
Regards,
Yogesh Redemptor
Attachments:
Save Excel Workbook Before Close.vi ‏13 KB

Excel save as pdf hangs when launched through a watch folder

Hi there,
I've configured a watch folder to launch a batch file which launch a .exe file I've written in C++
In this application I launch Excel which open a .XLS document which contains macros.
At the end of the computations there is a macro which save as pdf.
At this point everything hangs and I have to cancel the job I've created for the watch folder.
If I disable the watch folder and I place the starting file inside the watch folder
and I manually launch the .bat file (which usually is launched by the watch folder) everything works perfectly.
I really really hope there will be someone here coming with a solution for me.
By the way on the windows forum I've got a very disappointing answer where they stated it was probably a fault of my application.
Well fortunately that was not the problem because
I can reproduce the problem even removing my application from the equation so now we have cleared
the issue is not casued by my application.
So if you want to try it yourself just follow the steps below:
1) create an excel document so that after you open it it automatically run a save as pdf operation and close excel. (let's call this document "PRINT_TEST.xls")
2) create a batch file named "Excel_launcher.bat" and write the command
""C:\Program Files\Microsoft Office 15\root\office15\EXCEL.EXE" "C:\teststampapdf\PRINT_TEST.xls""
3) Now create a watch folder job that execute that batch file.
something like "C:\watchfolderX\Excel_launcher.bat"
4) now create a watch folder that uses that job and for file filter use "*.txt" enable it and start it
5) now launch manually the batch file and you'll see that it print the pdf and closes itself
6) drop a txt file inside the watch folder you've created and you'll see it hangs at the save as pdf operation.
This is something that have to be fixed and it's due to excel.
I can launch and save documents with all the application I want but excel so that's the problem.
Please take a look and keep me updated I badly need to find a solution for this issue.
THANK YOU in advance,
Davide

Hi Davide,
This is no the right forum for your issue. I think you can consult this issue on some Excel end-user related forum.
Best regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Excel Save As dialog not appearing for one user

Hi,
My company uses a payroll application called Cintra.
It's possible to run a report in this application and
export it to Excel.
When one of the users exports a report and clicks File > Save As > Browse nothing happens. All other users get the Save as dialog.
Is there any setting that may be preventing this? She does not appear to have this trouble when saving any other
Excel
files.
We all use Excel 2013 on Windows 7 in Citrix.
Cheers
Paul

Here is an article for troubleshooting errors when save Excel files you can refer to
http://support.microsoft.com/kb/271513
Based on your description, it's most likely that a Third-party add-in causes this issue, you can try to start excel in safe mode to test it. excel.exe /safe

Excel save as

This is a 2 part question:
1. I have a VI that writes data to excel but i want to leave my original file intact and save as different name, i keep getting an error
2. for the new name i want to append a timestamp but cannot find how to get the PC current time
any help would be appreciated, i've attached the VI and a sample spreadsheet
i'm using LV 2012 and office 2007
Solved!
Go to Solution.
Attachments:
ExportToExcel_new.vi ‏34 KB
Example.xlsx ‏9 KB

You could always drop a property node to get the values from the chart and then write to a csv file. Or, you can also always right click on a chart in LabVIEW and choose to export to Excel.
Jesse S.
Applications Engineer
National Instruments

Excel save as txt

Experts,
I have a client who wants to save reports to Excel. This works from SBO, the report is auto opened by Excel. If they close this it is saved to TXT. They want this to save to Excel instead of TXT format without them having to 'save as'.
Is this possible?
Thanks,
Marli

Hi Marli,
Export to Excel function is always export file as text file. Only the macro in Autoopen.xls make it open and displayed in Excel worksheet. It has to be saved as Excel file before it closed.
Thanks,
Gordon

Excel Save As functionality using ABAP

Hi Gurus,
I have an Excel file on Presentation server. I need to save this file in specified directory in Presentation server (Means Save As functionality). How can I do it in ABAP.
Is there any API available. Could you help me on this.
Thanks,
Rayudu

Hi,
To upload the Excel file, please refer this thread :
Re: Upload excel file
To download the Excel file on application server, please refer this thread :
Excel download in Application Server
To summarize :
You need to use GUI_UPLOAD to upload the excel file and need to use FM MS_EXCEL_OLE_STANDARD_DAT to download the excel file on application server.
Best regards,
Prashant

Excel toolkit --excel save.vi is broken arrow

Similar Messages

Maybe you are looking for