Michael Aivaliotis

Have you browsed the VI's in the LV palette? You never know what you might find. Perhaps this is not the complete solution but hey...

It works fine for me in 7.1. The Tmp_Called.vi unloads itself properly. There were some bugs in 7.0 that were fixed in 7.1. Also, try using the older method of closing the panel. I've attached an image that shows the Front Panel Open Property set to False. You also don't need the Abort VI method. Remove this. As a general comment, I'm struggling to figure out why you are jumping through these hoops. There are simpler methods to acomplish your goal. Have you investigated queues or notifiers? These open a named reference that is easier to manage.

I know that OpenG builder allows you to import an NI build file. This means there is code out there to read this info. Why not download the OpenG builder and poke around? Of course, the real question is, "why do you need this?" Perhaps if you let us know, we might find another solution to your problem.

If your text file is a tab delimited file with new rows seperated by carriage return and linefeed, then you can simply open it from Excel. Excel should recognize the format and load it up without problems. The other option is to do activex com to Excel and pump the data directly into Excel. This option may take several days or weeks to get working (if you've never done this type of thing before). This method is cool, you will grow as a programmer and you can impress others with the new knowledge you have attained. Of course your boss might yell at you for pushing out the deadline on delivery...

Yes, it appears to make it through intact. Interesting however, LV doesn't color it light blue. This would lead me to believe that there is a mask in place. Well, I know PJM_LabVIEW has built a tool here that pulls everything out. Let me try that... Ho hum... Oops, LV8 throws an insane object error!! :ninja:

Hey, I was browsing around to see what new scripting stuff is in LV8.0 (the old ini keys seem to work) :thumbup: . I couldn't find the diagram reference property. Has it been moved... or removed? Also, I noticed a nice feature. All the private methods and properties are now light blue in color. This will be nice for quick recognition of scripting stuff in your code.

I've updated all the links to Jim's new posted location. It should work now. BTW, I used Firefox default download system and it worked the first time, perfectly. :thumbup:

I guess we made the classic blunder of debugging 101: is it plugged in? Of course GPIB will not work without VISA. I guess you take certain things for granted after a few years. CVI includes all support modules? Even the entire VISA install? I haven't built an executable with CVI, if you have, then you probably know better. There is one simple workaround... don't use VISA. Use the basic GPIB functions. I've been using them on and off for over 10 years now without any headaches. Of course there are good use cases and arguments for using VISA. However, none of those arguments justify their usage in the applications I have written.

The important thing to note: The front panel of Tmp_Called.vi MUST be opened before it can register for events. So the panel must be opened and then the Vi must be run. Also why not send a TRUE event to BooEve? How can you tell if it's working if you are sending a FALSE?

Hmm, If you look into you 6.1 Installation CD, you will see a folder called LVAppBuilder. Have you tried running the LVAppBuilder.msi that's inside that folder? I can't see why you would get this issue if you just run that installer. Another option is to run the installer on another machine and then copy the App Builder files into the machine that needs the app builder. I don't think registry keys are necessary for App builder to run.

Since when? This is not true. NI's web server supports Mozilla browsers as well. Where did you get that information from?

It worked fine for me on the first try. I guess you already primed it for me huh? :thumbup: I guess the drivers portion is not included with the download eh? It prompted me for it. BUT, this time, the installer doesn't abort the installation if the driver CD is missing. Unlike 7.1 which uninstalled everything if you didn't have the driver CD.

Is there a way for you to verify that the VISA constant is populated with the values you assume are there in an EXE? I would make that contant a control and bring it up to the GUI. Build an EXE with it like this and then you know %100 that the VISA control has this populated properly.

I like your avatar. What did they call those things? curiously large rodents? Don't remember but it was funny. One of my many favorite movies. Getting to the LLB stuff now. I would say ditch them... However it seems like your employer is stuck in the stone ages for some reason. I'm curious, do they use source code control? I bet not. Otherwise they would not be using LLB's. How can you do source code control on individual files when they're wrapped in an LLB. Don't forget the dangers of LLB corruption! This is the biggest gotcha in LLB's. When VI's are saved into LLB's the file must be kept open and if there is a glitch during the save, the entire LLB is toast. There go all your VI's. NI support can fix this but who needs the hassle?

So LV takes this time to close... so? What's the problem?

Have you tried running the close datasocket server VI?

I see you've been using OpenG Commander. In your attached llb, there are some missing strict-type controls. Can you re-save it with those?

No, I didn't like it for Burt Reynolds. I liked it as a movie in general. Yes the sex scenes were enjoyable, but the rest of the movie was great too. As far as my wife, actually her favorite part was the final scene. Her eyes were bulging while I was looking down trying to figure out what was wrong with me... hehe...

Well I'll be a monkey's uncle! We have a bonafide bug...

Thanks for the contribution to the forums... this type of generosity makes me feel all warm and fuzzy inside...

This is fishy. If there is a breakpoint then LV will find it. Can you send the VI or a picture of it? I have a hard time believing this.

Interesting concept but impractical I think. Reducing complexity into a subvi is not a mechanical task isolated from its surroundings. It has to make sense. The VI must encapsulate specific functionality.

If you start from scratch then it's totally unnecesary. You must have standards to confine your diagram size. If you don't then you're asking for diagram chaos. The standards should evolve based on screen hardware developments but they still should be in place.

uhum... you tried to hide it in the image, but I can still tell what version of LV you're running... :ninja:

I guess the NI based bot lost? The NI marketing folks are mourning...