Open VI Reference asking save option

Hello,
I am opening a VI reference to analyze the state of the VI and closing it back and repeating this process for the bunch of VI's in a folder.
While closing the VI reference, it is throwing save dialog box for the some of the VI's, after closing the dialog only it is analyzing the next VI. To stop this behaviour I have set the Open VI reference Option to 0x20, but still it is coming. Please Give me some way to prevent this.

Are there any additional dialogs?
My assumption is, that those VIs are deriving from older LV versions and are not masscompiled to the current version you are using. Therefore, if you open the VI, LV developement environment will automatically recompile them, which will change the VI. So when unloading the VI, the developement environment will ask you to save unsaved changes (recompilation) of the VI......
Using the parameter 0x2 for opening the VI reference only effects the loading (supress the search dialog for subvis, do not mistake that with the "Browse for SubVI" dialog!), not closing the reference.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Similar Messages

Would like to allow PDF files to open straightway in the browser rather asking for open save option. pls help

I m running a website on intranet. while accessing pdf file more than 8 MB in size. A window having Openwith, Save option pops up. i would like firefox to open PDF files of any size strightway in the browser without pop ups. Please help
Thanks in anticipation

kearly - thanks a million for posting both the question & the reply! I just unchecked that little box by accident, & couldn't figure out for the life of me how to fix it. Thanks again!!

"Open VI Reference" Option "Prompt user to find missing subVIs"

I am using "Open VI Reference" to dynamically load a VI. For the "option" control of the "Open VI Reference" node, I pass "0x10" or "10" in hexadecimal, which supposedly "prompt user to find missing subVIs." Nevertheless, I don't get a prompt message dialog when I intentionally pass an invalid or missing VI path. Instead I just get an Error Code 7. What does this option "Prompt user..." suppose to do?

Make sure you set the properties on the integer input into the “options” control to the “Open VI Reference” to be a Hexadecimal format (right-click on the “options” control input, select Format and Precision…, then select Hexadecimal). Now, if you re-run your VI and wire in a VI with a missing subVI, the Open VI Reference will appear with a dialog that will prompt you to browse to the missing subVI. This is exactly the same message LabVIEW displays when it attempts to open a VI and cannot find its subVIs.
I’ve attached a simple example program to demonstrate. Enter the path to the “number extractor.vi” as the VI to open. You should see a dialog prompt appear asking for the “Search 1D Array – Complete.vi”.
Hope this helps!
Attachments:
openVIRefExample.zip ‏20 KB

How do i get the "open with" option back for pdfs after accidentally hitting the save option which now automatically saves any pdf?

Normally when I click on a pdf I would get an option to "Open With" or Save. I usually just opened pdfs first. I accidentally clicked on the Save option in this dialog box and now when I click on any pdf it automatically asks me where I want to save it. I want to get the "open With" option back, because I don't necessarily want to save a copy of every pdf.

Mountain Lion was released in 2012, so I suppose there might be advice in old threads or on the Apple forums if you don't get a response here right away.

When i exit, mozilla will prompt me a message asked if i would like to save my tabs(i have 13 tabs opened). may i ask, where does all those 13 tabs (web addresses/links) stored in mozilla, or in which file that i can locate in mozilla's folder? I need a s

I have a problem with my bookmarks, cookies, history or settings
Description
When i exit, mozilla will prompt me a message asked if i would like to save my tabs(i have 13 tabs opened).
may i ask, where does all those 13 tabs (web addresses/links) stored in mozilla, or in which file that i can locate in mozilla's folder? I need a solution that i can find/copy down that 13 web addresses without needed to open mozilla browser.
YOUR ATTENTION TO ABOVE MATTER IS VERY MUCH APPRECIATED!
PLEASE HELP!
== User Agent ==
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729)

Please see '''sessionstore.js''' in your Firefox profile directory, the location of which is described in the [[Profiles]] knowledge base article. This file can be viewed in a readable format using the [https://addons.mozilla.org/en-US/firefox/addon/10869/ JSONView] add-on.

How can I make a CC Illustrator file open in CS6? Save as does not give an option to save as a CS6.

How can I make a CC Illustrator file open in CS6? Save as does not give an option to save as a CS6.

No VIs listed for VI option in "Configure Open FPGA Reference"

I have a cRIO and I was using the Open FPGA Reference function to load a bitfile by specifying the VI name. This was working fine.
I have been compiling all day, and I just deleted a control and then changed a DMA FIFO datatype. When loaded and ran calls to the FIFO returned an error. So I tried refreshing the VI specification, but now when the dialog comes up, there are no VIs listed.
No idea what's wrong here.
Solved!
Go to Solution.

1) I commented out the FIFO when I compiled (forgot to switch it back on); so that's why the error occurred. Whoops.
2) I still don't know why I could not browse for the VI, but I was able to drag and drop.

What is the logic for the behavior of LV9 when opening vi references?

I recently started using LV 9 and I can't figure out what the rationale is for the LV 9 behavior when opening references to vis. The way I understand it, LV9 looks up vis using the absolute path on the disk where they came from when opening references, even if they are in memory. If just a vi name is given, LV9 tacks on the path of the referring vi on disk when trying to open the reference. So, as far as I can see, either an application opening references to vis needs to specify absolute paths to the location on disk and be modified whenever a dynamically called vi's location on disk is changed, or a dynamically called vi has to be saved in the same directory as the vi doing the calling or in a rigid and inflexible directory structure.
Example:
I am trying to use a 3rd party library whose vis open a reference to a vi that I create, the name of which is obtained from those in memory using a name pattern. The library vis get the name of the vi I created and try to open a reference to it. Previously this worked because LV looked in memory for "my.vi" when opening the reference but this fails with LV9 because it apparently looks for, e.g., "D:\VI\3rdparty.llb\my.vi", not "my.vi". So, as far as I can see, I have to save my.vi in 3rdparty.llb in order to use it. And, if I want to use 3rdparty.llb in another application, I have to save other vis to 3rdparty.llb or create a new copy elsewhere and save to that copy for the new application. A similar situation would occur if I passed the name of my vi to the 3rdparty.llb vis - either I would need to pass an absolute path and modify my application if I ever want to move my.vi, or save it in 3rdparty.llb.
Another example:
I have a large application built into an executable that calls up to ca. 60 vis using references. Previously I could just specify the path to the executable, and I could easily open references to my vis. Now (if I try to use the LV 9 file structure), I can't figure out the paths I need to open references. Either I have to specify the absolute path to the original location in my development directories, or I have to store all my source vis in some particular directory structure. If I want to reuse my vis in other applications (which I do) things would get pretty complicated. Likewise if I want to optionally open references in other vis than my top level vi (which I do), it seems well nigh impossible.
Basically I am struggling with the concept that an application remembers the directory structure where the source files were located, and/or depends on a particular directory structure of the source files to work. Maybe I'm missing some tricks that would make things easier, but someone will have to explain to me why these are good things.

I appreciate the responses and explanations. I've certainly learned
some things. I have extensive experience using LV but over a fairly
narrow set of
applications so I'm certainly not aware of many of the possible
techniques. I clearly don't use LV in the same way as what appears to
be the mainstream for LV programmers.
I have some additional
comments on the various responses:
"But
with VI libraries and LVOOP this had the problem that multiple VIs could
end up with the same name..."
I'm not clear what this means exactly. My first response would be
that it doesn't seem like a good idea in general to use different
portions of code with the same name in a single application. I'm
surprised this is even possible. I don't think LV will even let me
build from a project in which it finds name conflicts for vis.
"In addition to what Rolf wrote, it should be
pointed out that LV should NOT be looking for files if you built your
app correctly. Each VI maintains a relative path to all VI it calls and
it should know exactly where to find them (assuming they're there).
I think this illustrates one thing I was talking about. The
assumption appears to be that the organization of your source files is
an essential ingredient in the application that is built, which is a
foreign concept to me. My project file knows where all my vis are, the
applications build correctly, and, using the 8.x and previous file
structure for my exe, they work, and have for some time. As far as I'm
concerned the main point of using a project that identifies my source
files is to be able to pull in code from different places - if I want to
use a different version of one of my dynamically called subvis, from a
different location, for example, I tell the project file to use the new
version and rebuild. In your scenario, as I understand it, I'm not sure
why a project file in which you identify source files is even needed,
if LV already knows everything about the components of the application
you're building. As I mentioned, my primary application uses ca. 60
dynamically called vis. Most of these control different subsystems of a
large distributed hardware control and data acquisition system. All of
these are used sometimes when the application is used, but pretty much
never all of them at once - typically something like 10-30 of the
user-interactive vis are run at once. There is some communication
between them using globals, queues, and semaphores and such, but for the
most part they are independent and I test them separately. Until the
application is built and used, there is no need to run the entire
application including all subvis, and I never do it. When I build my
application, the app builder finds all the vis I specify and constructs
the exe file including all the vis I've told it about. Before LV 9 it
never occurred to me that I might actually have to worry about being
able to find vis inside the executable.
"However as tst has mentioned having an
executable search for VIs is a VERY VERY bad idea as it can break your
entire app if it happens to find the wrong VI at some point."
I don't really follow this point at all. Where are these vis
masquerading as the ones I want that will break my application? The only
vis on the machines where my applications are used are there because I
put them there inside the executables. I certainly would never use
different vis with the same name in an application - as I said above, I
don't even know if it is possible, and don't want to find out. Search
paths to find components like shared libraries are a common thing. It
doesn 't seem like a stretch for the run-time environment to define a
default search path like "somewhere in the exe file containing the
application".
I don't want to make a mountain out of a mole hill here, as I said
before, I am happy as long as NI supports the 8.x file structure, but if
nothing else I have definitely learned to appreciate how different
executables built w/ labview are from executables constructed in other
systems.

"Save" Option pops up while Submitting

Hello Friends,
We have a functionality where there is a form(Adobe Interactive), and when the user clicks on the "Submit" button
the fields data in the pdf form should get attached as xml in the mail.
Now when I test it by clicking on the "Submit" button, a pop-up comes up asking me to save the pdf.
Once I save the pdf, there is no conversion of xml and attachment to the mail.
On the other hand, If I do not save the pdf and cancel the "save", it gets attached to the mail as xml.
I wonder why the "save" option pops up.
Is there a way where I can disable it ? And design the functionality wherein the "Submit" button directly
attaches the content to the mail in xml.
Please let me know guys.
Regards,
Sanjay

Thanks for your quick response yesterday! After chatting with our official IT guy, He lined some things out for me. We are using SQL 2005. We discussed working up a program to add our data directly, which is an option. It will take some learning on my part, and I am willing to do it.
It would be optimal, in my mind, to use our web version in conjunction with Labview. But the more experienced person might know better.
When I call up our webpage on the front panel, I am able to navigate it by clicking around just like a normal browser. Using this method, the refresh issue I mentioned in my original post is not a problem. It refreshes with no pop-up. BUT I lose the capability to place my data into the fields. I am assuming the reference at the property node before the data placement is incorrect. (pictured below)
Is there a way to physically navigate a webpage and then use Labview to find the reference of whatever page I am currently on in order to place my data? This might be the route I need to go.

Save Options a Bit Confusing

Hi,
I've been using LabVIEW for about 7 months now, and am still a bit confused about the save options. It seems that whenever I modify a sub-VI for my app, the previous sub-VI I created ends up with the same settings that I changed in the newly modified one.
Example: I use an existing VI created by Daytronic Corp for monitoring a binary signal. I change the channel and a few other settings, and name the file oil press.vi, saving it in the new folder I created for my app. Then I close the oil press.vi I modified, then close the original, unchanged VI without saving it. When I create another VI starting with the original, unmodified one again, and save it using the same procedure, but using a different filename (let's call it fuel press.vi), oil press.vi takes on the characteristics of fuel press.vi, although the filename is still oil press.vi. So, I end up having to use the "replace" option on the block diagram and select oil press.vi as the replacement file. I have to keep doing this for every sub-vi I create.
This take a lot of time and is a bit annoying.
I hope you can understand what I'm saying. The Save options seem confusing to me, with all the references to keeping a vi in memory, closing the original, etc. Is there some text or a tutorial online that explains the save options in a simpler, more direct form? I have even read about it in my book (Labview for Everyone) and it doesn't go into much more detail about how saving the Vis actually works.
Thanks!
Todd Munsell
Turbine Engine Test Technician/IT Tech
Wood Group Pratt & Whitney Industrial Turbine Services, LLC
Plattsburgh, NY

Hi Mike,
Actually, I'm using LV 8.5. It's the descriptions of the save options that are slightly confusing. The information about what's left in memory and what's closed and opened is what's got me baffled.
For example, what, in layman's terms, do each of these options below mean... exactly? I would think that an option that simply says "Save as path/filename" would be enough. Then, the renamed, saved file stays open, since that's the one that's currently being used, and the original is closed and left as it was. Which option (and sub-option) would I choose to do this?
The number of options below seems a bit excessive, and not very clearly defined, at least to me. Even the explanation in the book "LabVIEW for Everyone", which is supposed to be for beginners, doesn't do a very good job of describing exactly what each option does. Thanks again!
Original file—Displays the path to the open file. You can
use this field to determine the location of a file on disk.
Copy—Creates and saves a copy of the file in memory to disk with a name you
choose. If you enter a new file path or name for the file, the original file on
disk is not overwritten or deleted.
Substitute copy for original—Both the original file and the
new file exist on disk, but the original VI closes and the new VI opens. Use
this option if you
want to create a copy of the original file and immediately edit the copy.
Caution If the original file has
calling VIs in memory, this option updates all these callers to refer to the new
file.
If the original file is in a project
library or project, this option substitutes the new file for the original in the
project library or project.
Create unopened disk copy—Both the original file and the
new file exist on disk, but only the original file remains open in memory. Use
this option if you
want to create a copy of the original file but continue editing the original
file, for example, if you want to create a backup copy. This option does not update
callers in memory to refer to the new file. You can update callers manually by
finding all instances of a
VI and updating the name of each instance. If the original file is in a
library or project, this option does not add the new file to the same library or
project.
Open additional copy—Both the original file and the new
file exist on disk and are open in memory. You must give the copy a new name,
because two files of the same name cannot exist in the same application instance
at the same time. Use this option if you want to create a copy of the original file,
continue editing the original file, and also immediately edit the new file. This
option does not
update callers in memory to refer to the new file. You can update callers
manually by finding all
instances of a VI and updating the name of each instance. If the original
file is in a library or project, you have the option of adding the new
file to the same library or project by placing checkmarks in the appropriate
checkboxes. If you place a checkmark in the checkbox to add the copy to the
library, the checkbox to add the copy to the project is disabled and
unchecked.
Rename—Renames the file in memory with a new name you
choose. This option
closes and deletes the original file and opens the file with the new name, so
only the new file exists on disk and in memory. Use this option if you want to
change the name and/or location of the original file.
Caution If the original file has
calling VIs in memory, this option updates all these callers to refer to the new
file.
If the original file is in a library or
project, this option adds the new file to the same library or project,
and removes the original file.
Duplicate hierarchy to new location— Use this option if you want to
save the original
VI and its hierarchy to a new location. You might want to rename the new VI
hierarchy after duplicating it.
Message Edited by tmunsell on 08-09-2008 01:54 AM
Message Edited by tmunsell on 08-09-2008 01:56 AM
Todd Munsell
Turbine Engine Test Technician/IT Tech
Wood Group Pratt & Whitney Industrial Turbine Services, LLC
Plattsburgh, NY

Export with save option

Hi,
Iam using IR 11 version. I have written script for exporting chart and pivot data.I used command button to export.Whenever i clik on the command button its exporting successfully but i want to save the files in different locations.for example.. if i clik on the command button it should ask for where to save the file.
script which i have written for export files..in this where i need to keep the save option???
try{
ActiveDocument.Sections["C_TTT"].Export("C:\\TTT.jpeg",bqExportFormatJPEG)
ActiveDocument.Sections["P_TTT"].Export("C:\\TTT.csv",bqExportFormatCSV)
Alert("exported successfully")
}catch(e)
Alert("Failed To Export")
}

When you click on a method in the Script Editor it tells you the required and optional parameters in the lower left corner of the editor.
And if you click Help after clicking on the Method you get the following:
Export (Method)
Applies To:
ChartSection object, (CubeQuery) QuerySection object, DataModelSection object, Document object, DashboardSection object, OLAPQuerySection object, PivotSection object, QuerySection object, ResultsSection object, Section object, TableSection object, ReportSection object
Description:
Creates a file with the information from a section object. Files can be created using the standard data formats from the BqExportFileFormat constant group.
Note:
For UNIX users of the Export and ExportToStream methods,Interactive Reporting Web Client and Interactive Reporting Web Client reference the umask command of the user running the Interactive Reporting Service to determine the three-digit octal code. This code defines the read-write-execute permissions to be turned off. Typically, umask is used in .login or .profile and in the Bourne and C shells. It is a built-in command.
Syntax:
Expression.Export(Filename As String, [optional] FileFormat As BqExportFileFormat, [optional]IncludeHeaders As Boolean], [optional] Boolean Prompt), [optional] BqEncoding Encoding)wayne

Lync2013 mobile on android wont wake up if screen power saving is activated in power save options.

Lync2013 mobile on android wont wake up if screen power saving is activated in power save options.
Issue was reported by cutomer and reproduced by me.
Customer reported this on devices:
hTC /android desire x
samsung core 2
motorola
My app version: 5.5.3.8935 on samsung S2.
Is this a known issue? I wasn't able to find any references on inet about this issue.
// edit: updated to version 5.5.3.8960. Looks like it is resolved for me. Customer still reports problem with version .8960.

Hi,
You can feedback in the link below:
http://blogs.technet.com/b/lync/archive/2012/11/01/lync-app-feedback-you-asked-and-here-it-is.aspx
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

Error 7 occurred at open vi reference in New Report.VI

Hello!
I use the report generation toolkit on LabView 7.0 to create a report in Excel. The program works fine until I make an executable version. I the get the error:
Error 7 occurred at open vi reference in New Report.VI
I use the New Report.VI, Bring Excel to front.VI and Save Report To File.vi
Can you pleace help me!!!

Most likely, you did not include the required libraries in your build script. When building an executable in which you use the Report Generation Toolkit, you must include the _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs on the Source Files tab.
Check this article for more info.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/86256a47004e16d186256a84004cb883?OpenDocument
Daniel L. Press
PrimeTest Corp.
www.primetest.com

"Open Vi Reference" generates a Error 7

Hello,
I am getting "Error 7" from the "Open VI Reference" vi, the name of the vi is wired vi path input. The "Error 7" means that the vi cannot be found. So I went to "Tools ===> Options ===> Paths" and modified the Path so that Labview can find it. But for reasons I do not understand the vi I want to get a reference for cannot be found. So it leads me to beleive that the "Open vi Reference" does not use the path option to find a vi. Any ideas what is going on?
Regards,
Kaspar
Solved!
Go to Solution.

Hello,
Thanks for getting back to me. I have attached a file fo the screenshot of the Block diagram. The "Open Vi Reference" is in the upper left hand corner, which generates a error when I have updated the path options to point to where the file exists.
Regards,
Kaspar
Attachments:
vi_error.GIF ‏21 KB

Updated to iOS 7, when my phone came on for the first time I could see I had 2 new viber messages. When I went to open viber it asked me to register my number, which I did. Once the app was open I noticed all my message history was gone.

Hi,
I have only just upgraded to iOS 7 on my iPhone 4 and am having a problem with Viber. When my phone came on for the first time after the update I could see I had 2 new viber messages, when I went to open viber it asked me to register my number, which I did. Once the app was open I noticed all my message history was gone...
I still have an itunes backup of my phone just before the update, I restored it to this backup, followed the same process and now viber will not even work (the access code wont sms to me and the phone call option for recieving this code also come up with some error about not being able to do this at this time).
I have been able to access viber using another phone number (I have two sims which I use as I am currently overseas in south korea, my referenced australian sim has worked previously on viber overseas and I definently do have roaming on) but again I have no message history.
So to questions:
1) Why is my activation not working under my referenced australian number?
2) Can I recover all my message history which should be saved in my itunes backup? I am willing to revert to this backup state again if needed.
Please help.
Thanks.

Look iTunes>Preferences>Devices...is a backup listed for your iPhone 5 dated BEFORE you restored your iPhone 4 backup to your iPhone 5? If not, your data is gone. If there is a backup, on your iPhone 5: Settings>General>Reset>Erase All Content & Settings. You should now be able to restore that backup, if it exists, to your iPhone 5.

Open VI Reference asking save option

Similar Messages

Maybe you are looking for