linnx

QUOTE(PJM_labview @ Sep 28 2007, 04:57 PM) Yep got it, thanks.....was a little confusion.

Hello, I've spent several hours on the phone with NI today trying to find out how to debug/trace execution of a VIT (vi template) with no results. The engineer helping me, skipped out on me and was unreachable through the end of the day. So basically I have a little problem with VITs which in our application are used as displays which spawn an x amount of displays and show data curves which are read from our memory list. Basically I’m putting in some functionality right now and I want to be able to trace the execution flow (see the code on the BD or put in a break point) of the display instances which get created from say…XY Graph.vit. I know there’s a way to do this b/c NI said it’s a new feature in 8.2.1 and supposedly they fixed a bug in it in 8.5. I called NI “platinum” support line (they should just upgrade straight to triple uranium since platinum is useless). Any ideas? Thanks!

QUOTE(crelf @ Mar 6 2007, 04:41 PM) Sometimes I like to think that when I'm posting here, i'm not making a report for the NSA or DOD, alas. The price of the Run Time License is the cost of the deployment, so if you have DIADEM basic for 1199, the user has to pay the same to use your application. The price of DIAdem can be found here: http://www.ni.com/diadem/''>http://www.ni.com/diadem/' target="_blank">http://www.ni.com/diadem/. The lowest price is $1199 which is steep considering that most languages out there come with great built in classes for print preview and other basic stuff like this. DIAdem is overkill and it seems like you get overkill or nothing, there's no inbetween as far as LV's print preview functionality and formatting is concerned.

Hi, I need to be able to programatically call LV's Print Preview function (the one you see when you do a File -> Print -> Next -> Preview). LV seems to make it extremely difficult to do any kind of print previewing. Also I wou ld like to be able to modify that VI b/c we have a case where there are multiple sub-vis we would like to print which are on the screen and we want to see a print preview of that. Kind of like a WYSIWIG print editor. Any help is greatly appreciated. DIAdem express vi is out of the question b/c you need DIAdem and that means a run time license for users, that is a prohibitive cost. :headbang:

QUOTE(Herbert @ Jan 19 2007, 08:24 PM) The unfortunate part of DIAdem Report Generation Express VI is that it requires DIAdem. My company was considering puchasing it but then we found out the cost of User Run Time licensing. You have to buy licensing to deploy DIAdem to users and that is a big problem. NI should really relook this part. I mean this is too much money. So without DIAdem that express VI is useless, alas very nice if NI wasn't so greedy.

QUOTE(Herbert @ Mar 5 2007, 04:33 PM) Thanks Herbert! What i'm really interested in is that little Preview window on Configure DIAdem report VI. Is that accessible and it's not pwd protected, hopefully ;-) Thanks.

QUOTE(Herbert @ Feb 21 2007, 06:19 PM) How do i modify an express vi's block diagram??

QUOTE(PaulG. @ Feb 21 2007, 10:40 PM) Thanks a lot Paul! That sounds exactly like what we want/need. Jim sorry for cross posting, I will make sure to put a link to NI next time. I just feel like this is the best way to get an answer b/c often times NI's forums are non-responsive and sometimes I don't get anything on Lava.

Hi, I need to create a report tool with a print preview capability and ability to print a very simple report (not html,word or excel) that would print straight to the printer after the user had a chance to preview it and move around the objects dynamically (maybe in the same preview window) and am currently failing to see anything that comes standard with LV8.2. I'm talking about creating a WYSIWIG (what you see is what you get) type of report with an ability to rearrange items on the screen and then doing a print preview with movable page borders, zooming, etc. I was thinking of using some .NET classes but am not allowed b/c we'd have to include the framework or make users download it (ppl with win2k machines) which is a problem and cannot be considered. Anyway, I was wondering if anyone can recommend any good 3rd party reporting package that's ActiveX compatible or any recommendations would be greatly appreciated.

QUOTE(jhoskins @ Feb 13 2007, 06:06 PM) Hey j, That romulus guy is me ;-) So i just cross-posted myself hehe. Still no answer, here's what I added there: ========== Thanks for the reply. I do understand how bizzare this must seem to you, I had the same reaction. I know perfectly well the behavior of LV built exe, been using it for 5 years. The problem here is the bizzare behavior of the .exe (any in fact, i've built several test vis and exes) on 3 different machines. I'll try to explain what's happening: 1) I create a new project 2) I add my Test.vi to the project 3) I set my Test.vi as the startup vi (Test.vi simply calls my main vi via the vi reference). 4) I build the exe and execute it 5) Upon execution, an LV 7.1 splash screen pops up for a brief second and I get an Open VI file dialog box asking me to select a VI I want to open, all the VI files inside that window take on the appearance of LV7.1 icons, instead of 8.2. If I try to select a VI from that window, I get LabView load error 9: VI version (8.2) is newer than LabView version (7.1). I'm used to that error after you recompile a 7.1 vi to 8.2, but I don't even have LV7.1 installed. It seems like the exe is trying to use LV7.1 RTE to run itself instead of 8.2. I though I have 8.2 RTE automatically installed by LV Dev, but I guess not since it doesn't show in Add/Remove Programs menu, but it DOES show up in MAX under software, go figure. I wish I could get someone in NI to look into this. I've never had a problem like this, it is happening on 3 PCs here and is taking up a lot of work time. I have source code I can send as well as a short video of what's happening on my machine.

QUOTE(Aristos Queue @ Feb 13 2007, 05:12 PM) Well we do have dlls, quiet a few of them but the NI engineer I spoke with, said that on his machine everything worked as expected and opened when he ran the exe. The problem with my machine is that even when I create a simple, new exe with a test vi, it flashes the 7.1 screen and gives the open vi dialog box. I'm going a little crazy at this point, will probably have to uninstall everything and use msiblaster. I can post pictures.

QUOTE(Tomi Maila @ Feb 13 2007, 03:03 PM) Yes. Everything was installed in proper order. I tried removing all of NI software this morning and then installing just LV 8.2. I still get the same thing. I called NI they don't know what might cause this. The problem is that it did this on 3 different machines. Basically it looks like windows doesn't want to associate vis with LV 8.2. I tries to use the 7.1 RTE to open all VIs after I run my exe and even if I try to force-associate VIs with LV 8.2 by manually browsing to the LabVIEW.exe i simply get taken back to the Open With dialog box and no version of labview is anywhere in that list.

Hi, I'm in the process of creating a new exe of our project. A strange thing keeps happening and I don't know what's wrong. I had LV 7.1 installed on the machine, as well as LV 8.2 to transition to the new version. I created an .lvproj and built a new .exe of our application. Lo and behold, it flashes the LV 7.1 flash screen and then asks me to select the VI I want to run, when i select the main VI of the application, it simply gives me an Error 9 message and says that that vi is compiled in version 8.2 of LV and won't open. I tried right-clicking on a vi and trying to force it to associate with 8.2, that didn't work. I uninstalled 7.1 and the 7.1 RTE entirely and when I try to run my LV 8.2 built exe it STILL manages to use the 7.1 run time from somewhere. After that I tried to re-associate them with 8.2 yet again to no avail. When i run my exe it just tries to open them in the non-existing 7.1 RTE and re-associates them all with 7.1. Please help, i think this is a bug. All the exe is, is a splashscreen.vi which calls our main application vi through the vi server. This worked perfectly fine in 7.1 (during distribution, we would just save all of our VIs without block diagrams). I really need some help with this one. Thanks in advance.

Hi, I need some help with the Project Explorer as its documentation is very poor and hard to find. I've created a new project file for a large project that I have to convert from 7.1's app builder .bld file. I tried converting the .bld file first, that of course failed and so now I've added the entire directory where our project resides to the project file of LV 8.2. When I refresh the dependencies I see that some files are marked as missing. When I right click on the file I basically get an option to open that file but when I do it warns me that it will open it but it will be removed from the dependencies list. I think the problem is that before we used LV 7.1 and the previous programmer took some NI's vi.lib files and ported a partial vi.lib into the application. Now LabVIEW uses library management and some of the previous files used are now under namespaces like NI_AABPro.vilib and other similar NI names. My question is how do I update the dependencies or how do I find what files are still pointing to the wrong files? I did a mass recompile obviously and changed most of the dependencies but obviously that's not enough, shouldn't the mass compile take care of stuff like this?! Thanks in advance.

Yen you're absolutely right, This has been my way of thinking from the beginning. However sometimes the most difficult part is convincing someone that changing the way they've done something in the past is good and positive and will keep you away from a lot of problems in the future. So thankfully the other devs have been understanding and we've decided on still creating an InstallShield project but one which will include RTE in one executable along with the application and one which will prompt the user to download it off the website as well as a CD version of the entire thing where space really doesn't matter. Thankfully a good point I was able to make is that if we make application-level updates in the future, the application will actually shrink by 40MB since we won't have to include our vi.lib and the user will already have the RTE installed.