Application Builder, Callback function and ActiveX

I have a software application which calls a callback function. This
callback function talks to an Activex component. When I try to build
an application.exe, the exe always hangs. Anyone know how to get
around this? In the Labview developement envirorment it works just
fine.
-Chuck

What is the ActiveX control that you're calling?
Where in the execution of the code does the program hang?
Can you post any of your code?
What version of LV are you using? What version of Windows?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Similar Messages

In application builder the top level vi is always set to "run when opened"; how do I turn this off so I don't have to change it each and every time I build a .exe??

I build a lot of executables using Application Builder under LabVIEW and in every one I build, I don't want the top level vi to take off and run when I open the executable. Currently, I edit each .exe I build within Application Builder and change the option of "run when opened" from Yes to No for the top level vi. All the other subvi's are already set to No. It would seem as though there should be some way to "turn this off" if you will so the top level vi is not always set to "run when opened" by default within Application Builder. Is there such a solution that anyone knows of?? Any help would be apprec
iated... thanks...

Indeed the Application builder forces "run when opened" to true for top levels VIs. If you don't want your VI to make any real work when the application starts, you should simply put a do-nothing loop in the beginning of the VI that will loop until the user presses a boolean. It will be more intuitive for users to press a Run button on the FP than clicking on the white Run arrow in the bar.
LabVIEW, C'est LabVIEW

Problem with "Application Builder"

Hello!
I have problem when I am using application builder to convert my program to exe files. MY PROGRAM: I use a main program to copy a template VI in to other VI´s, and then I can execute the copied VI´s from main. When I have tried to convert my program to a EXE file, everything works but not executing the copied VI. The following error messages apperies when I try to execute the copied VI. What does this mean???
BR
Kristian K
Attachments:
error.jpg ‏152 KB

Hello!
Information for users on this discussion forum: the problem was due to 'Build Text' function and when that function was removed the program worked fine. The functionality in the 'Build Text' function could easily be replaced by the 'Format Into String' function.
Regards,
Jimmie A.
Applications Engineer, National Instruments
Regards,
Jimmie Adolph
Systems Engineer Manager, National Instruments Northern Region
Bring Me The Horizon - Sempiternal

"file already exists in the destination" during application build

I am trying to build an executable and have gotten the following error:
The file already exists in the destination.
C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\Sentech LV 82\Shared Library - Trigger SDK\StTrgApi.dll
WHen I start the build I go to "Build Executable" then click "Build"
The VI for the project I have open is the Startup VI and I do not list any Dynamic VIs or Support FIles.
I am using Labview 8.2
I installed a user library for a USB camera from Sentech wich I am using and it works fine in Labview 8.2
When I try to do the build I get the error shown above. The file it is referencing is there along with the .lvlib file.
I tried removing the file shown in the error message to see what would happen and I continue to get the same error even though the file is not there. I even restarted LV and still got the same error.
I am new to the application builder (v7 ?) and have not been able to find any good tutorials. Does anyone have any ideas on this error or a good place to learn more about app builder.
Thanks
Keith

I am new to the application builder (v7 ?) and have not been able to find any good tutorials. Does anyone have any ideas on this error or a good place to learn more about app builder.
Thanks
Keith
Hi Keith,
you can check this Link out for a tutorial on app builder.
Regards,
Denver

Remove Application Builder while creating workspace in Apex

hi,
am using apex in 11g database,am creating a workspace but it contain application Builder,Sql Workshop and Utilities..
My objective is i want only sql workshop no need Application builder and utilities while creating workspace in Oracle Apex.
guide me
regards
apex

Ummm... OK. But why? If you only need a SQL tool why not use SQLDeveloper or some other tool? Is it that you want a web browser interface?
It would be very unwise to try to remove the applications you mention from the apex installation. This is probably possible but potentially very risky as the stability of your apex installation is concerned.
You might want to try taking a CSS approach and hide all the stuff you don't want to see via a custom CSS file that you could put in your installation.
Earl
P.S. If you're going to ask how to do this then it's probably not something you're ready to do.

I have a application build in labview 8.5 for Windows XP using NI Visa functions to interact with hardware , how to make is work in Windows 7 32 bit and Win 7 64 bit

I have a application build in Labview 8.5 which wroks fine with Windows XP , this program uses basic read /write functions of NI Visa to communicate with Hardware . This application doesnt work with Windows 7 32 bit/64 and Vista . What changes i need to do to make it work for the said operating system

srinivas wrote:
Sorry for confusion ,
My question is what changes i need to do in code or while making the installer to make the existing program work with other Windows operating system
You need to make sure the machine have the corresponding NI-VISA installed. Check in the NI software pages for the right version.
Also make sure that the com port's can be selected when you first start the application. Eg. if you refer to VISA "COM1" on the XP machine It might be "COM2" on the Win7 machine.
Br,
/Roger

Passing arrays with Call Library Function does not work after application builder

Calling a DLL with Call Library Function which requires an array of data works correctly in Labview, but after building an exe with application builder, the call no longer works. Dereferecing the pointer in the DLL retuns all 0s and not the actual values.
Solved!
Go to Solution.
Attachments:
TEST.zip ‏28 KB

I did not run your code because it is a little unclear to me what it does.
Two things:
First, is the DLL you are calling the DLL-ified version of PopUpNames.vi? Then the problem is likely that the panel is not being built into the DLL.
When LabView builds an application / dll, it strips the front panel and block diagram from all VIs that it doesn't think need to show a panel at run time. This reduces file size and increases code security. The App Builder's panel inclusion logic can be overridden by Build Specifications -> Source File Settings -> Remove front panel. A better method is to put a property node on a control in a window you want to show marking it "visible"; this is sufficient to tell the App Builder it should keep the panel.
Currently Source File Settings shows "no dependencies" (clearly incorrect---another evil side effect of Express VIs I guess) but if you change the settings as shown below to keep ALL panels, one might hope the App Builder can figure it to keep the panel when it deconstructs the Express VI. (Alternatively convert the Express VI into a regular one.)
A second comment: I am a bit flummoxed at the larger goal here. You are calling LabView DLL from LabView, which doesn't make a lot of sense, so I assume your larger goal is to call LabView from C or vice-versa. In that case be aware that your DLL is x86 (32-bit) but you are passing 64-bit ints as your pointers. In this case it is 32-bit LabView with 32-bit pointers in embedeed in 64-bit containers calling 32-bit LabView with 32-bit pointers in embedeed in 64-bit containers, so it all works, but if your going to call this from C or whatnot you're going to have to follow that same design.
When calling C code the LabView Call Library Function does have a "unsigned pointer-sized integer" data type that always appears to be 64 bits in the dev env but which actually passes a 64 or 32-bit int to the DLL depending on the environment. The "pointer sized int" has to be 64 bits in the "LabView" part of the code because LabView's strong typing requires the data type to be determined at compile time. Casting all pointers to the largest data type in LabView makes it possible to write platform-independent code, but down at the Call Library level you still have to put the right number of bytes on the stack.

Application Builder for labVIEW 7 Doesn't support any report generation function

I'm Using LabVIEW 7.0 to build an application My Application is exporting data to an excel report. the vis were working great until i tried to creat an .EXE file. The application is working fine but when i try to generate the report nothing happens.
So, I decided to test the report generation functions alone (New Report.vi, Append report text.vi and Dispose Report.vi). The Problem Still there, the .EXE file takes no action when i attend to generate a report. any suggetions please.

Shady Yehia wrote:
> I'm Using LabVIEW 7.0 to build an application My Application is
> exporting data to an excel report. the vis were working great until i
> tried to creat an .EXE file. The application is working fine but when
> i try to generate the report nothing happens.
>
> So, I decided to test the report generation functions alone (New
> Report.vi, Append report text.vi and Dispose Report.vi). The Problem
> Still there, the .EXE file takes no action when i attend to generate a
> report. any suggetions please.
Another possible reason besides of possible path problems: Are you
running that application on the same computer? If not you need not only
to install the Runtime-Engine (automatic when you create an installer)
but also the Report Active X support.
To include that into the installer
you go into the Installer Settings Tab, then press the Advanced button
and make sure that you check the NI Reports Support checkbox before
creating an application build.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Application Builder: What is the significance/function of "page sequence"?

Because we are always pressed for time, I have developed the nasty habit of glossing over things that may be opaque to me, with the mental reservation that I will re-visit the issue "when things calm down".
One of those opaque things is the function, significance, or use of "sequence" in the context of APEX Application Builder and application pages.
I am working through the Oracle-By-Example application labeled OBE_PROJECTS. I have created the Master-Detail form, but it has not come out as expected. According to the instructions, when I created the page, I designated the home page as its parent. Yet, when I run the application, the icon for the master-detail form does not appear.
I assume that I've fat fingered something when I built the page and attempt to correct it. I think that the answer will lie in the task "Reparenting page hierarchy". When I look at the "Create/Edit Breadcrumb Entry page", I see in the "Entry" region, that the Parent Entry is, indeed, correct ... that is "Home (Page 1)". On the other hand, the text box labeled "Sequence" is set to "10". And this is the same value as the Home Page itself. Can that be correct? Shouldn't my Master-Detail page have a sequence number subordinate to the Home Page?
Any help/elucidation will be appreciated.
Regards,
Gus

Varad,
I hadn't gotten that far yet. I'm still following OBE script and accessing the page from the "Run Page" icon in application builder.
The issue itself, pages not showing up, is solved for me. I had anticipated that simply declaring the parent of Master-Detail page to be home page would automagically make those objects appear on the home page.
Slogging through the Oracle By Example, I learn that one must actually edit the home page to have them appear (how barbaric!)
But, the question of exactly what "page sequence" means and how it's supposed to be used is still there.
Thanks for the Response,
Gus

Application Builder: Can you create non-blocking, return-immediately functions in a dll?

I need to include a procedure in a dll that is non-blocking, i.e. it should return immediately after the procedure has been called, and not return after its processes are completed.
The procedure is a LabView 7.0 VI, and the dll is being created using the Application Builder. Currently the procedure completes its desired task and then returns, but I would like the function to return immediately. Thanks for your help!

Rischaard,
I don't know if that will work in a dll, however as an idea:
use the vi-server functions:
Your dll-procedure opens a OwnTreat.vi(wich will do the work) with vi-server, and run it without waiting for completion.
First thing OwnTreat.vi should do is opening (with vi-server) a reference to itself (So your caller dll can close without stopping the OwnTreat.vi)
Then OwnTreat.vi con do what YOU want. When finished close the self-reference
Maybe you need a short wait or a feedback to make sure that OwnTreat has opened his own reverence before your dll stops.
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

Problems with Application Builder and NI-DAQmx drivers in Labview 8.2 Professional

Hello everyone,
I am trying to use the application builder to create an executable so that someone without labview is capable of a remote panel connection to connect to our test laboratory. our test laboratory uses the USB Compact DAQ 9172. I did find some other forums that ran into a similar problem where a computer that didnt have labview installed on it looked for a particular driver (nilvaiu.dll). The common solution appeared to be when building the installer, include the current NI-DAQmx (8.3 in our case) option and then the clients worked fine. My question is when i use the application builder to create an installation file for this application, i get a prompt to:
Locate the "National Instruments Device Drivers - February 2006 Disk 1" distribution. LabVIEW needs to copy a component installed or updated by the distribution to continue building the installer.
What is confusing is that the installation cd's in our laboratory are from August 2006 (501165N-03). It didnt make sense to me that i would need to downgrade the drivers from a few months ago, but i've been wrong before. We just upgraded from the full development to the professional version about 2 weeks ago to utilize the application builder function. Has anyone else ran into this problem and could this be a limitation because we purchased the software with the academic discount?
thanks in advance
Chris

Chris,
My "fix" is brute force. Backup everything. Removing all the NI software takes a while. Be sure to remove leftover directories and files.
Altering the windows registry takes seconds and is not hard if you know what you are looking for. I've attached a screen shot with the NI entry selected. This is what I deleted on by machine. The thing to remember is that the registry controls all the software on your pc. Delete/alter the wrong entry and you have problems. Worst case scenario is that you could end up formating the hard drive and starting over from scratch. I'm not trying to scare you, but I want to make sure you understand the potential for harm.
One thing you might try first. NI-DAQmx 8.5 is now available for download from NI. You might try unloading 8.3 and installing 8.5.
Attachments:
regedit pic.JPG ‏102 KB

Labview 8 Application Builder and VISA Runtime Engine

Hi,
I am using Labview 8 Application Builder and everything is working fine except for 1 small thing. My program makes use of some of the VISA functions and when I build the application I'm having to include the VISA Runtime Engine Installer as a separate item on the CD to make the .exe file work.
What I would ideally like is for people who want to use the application to run the installer and that all necessary components (including the VISA Runtime Engine) are also installed in the one installation. At the moment they're having to do 2 installations and I would like to streamline this.
Is this possible?
Ken

Hi,
this How-To explains about making those selections and including the different drivers :
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/add_installers_to_build/
and this tutorial covers the screenshots a little more step by step.
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

I am trying to write a double buffered data acquisition program using MFC and a callback function.

i am trying to do a double buffer data acquisition using MFC application framework in Visual Studio.i want to use a callback function to notify when the buffer is half full.do you have some sample reference program that can help me?

What DAQ board are you using? When you installed NI-DAQ you should have selected to install the support files for VC++. Then there will be several examples on how to do double buffered data acquisition.
If you have already installed NI-DAQ 6.8 or higher and did not select to include the support files, you can run the NI-DAQ setup program and just add them. If you are using an older version, you will have to uninstall and reinstall.
Once you have the support files, follow this path to the examples.
>>Program Files>>National Instruments>>NI-DAQ>>Examaples>>Visual C>>
If you are doing digital acquistion, goto the di folder, if you are doing analog acquisition goto the ai folder.
As for the callback function, you can use the NI-DAQ function Config_DAQ_
Event_Message with DAQEvent Type = 1, where N would equal half your buffer.
Brian

ORA-28112: failed to execute policy function - Error in Application Builder

Hey all,
I've added a policy function to one of my tables and now I'm getting this error when I try to update a report region that references that table.
"Query cannot be parsed within the Builder. If you believe your query is syntactically correct, check the ''generic columns'' checkbox below the region source to proceed without parsing. ORA-28112: failed to execute policy function"
If I remove the policy then everything works fine. My application also runs fine with the policy in place. I just get these errors in the application builder when updating a report or an LOV that references the secure table.
The parsing schema is APPL_USER.
Here is the policy function:
FUNCTION DOCUMENT_TABLE_POLICY (object_schema IN VARCHAR2 DEFAULT NULL
,object_name IN VARCHAR2 DEFAULT NULL)
RETURN VARCHAR2 IS
v_nt_seq NUMBER;
BEGIN
IF user = 'APPL_USER' OR INSTR(user, 'ITFC_') = 1 THEN
RETURN NULL;
END IF;
IF V('APP_USER') IS NOT NULL THEN
IF V('F_NT_SEQ') IS NOT NULL THEN
v_nt_seq := V('F_NT_SEQ');
ELSE
SELECT NT_SEQ
INTO v_nt_seq
FROM APPL_USERS
WHERE UPPER(NT_ID) = UPPER(V('APP_USER'));
END IF;
RETURN '(DOCUMENT_TYPE, MANAGED_BY_ELEMENT, PROGRAM_CODE, CONTRACT_NUMBER) IN (SELECT DISTINCT R.DOCUMENT_TYPE, USL.ELEMENT, USL.PROGRAM_CODE, USL.CONTRACT_NUMBER FROM IPRACA_USERS_SECURITY_LINK USL, IPRACA_SECURITY_ROLES R WHERE R.SECURITY_ROLE_SEQ = USL.SECURITY_ROLE_SEQ AND USL.NT_SEQ = ' || TO_CHAR(v_nt_seq) || ')';
END IF;
--UNAUTHORIZED USERS CAN SEE NO DATA
RETURN '1=0';
END;
This is how I setup the policy:
BEGIN
DBMS_RLS.ADD_POLICY(
object_schema => 'APPL_USER'
,object_name => 'APPL_DOCUMENT'
,policy_name => 'APPL_DOCUMENT_POLICY'
,function_schema => 'APPL_USER'
,policy_function=> 'APPL_SECURITY.DOCUMENT_TABLE_POLICY'
END;
Any help would be greatly appreciated!
Thanks,
Jonathan Hart
APEX 3.1.1

Thanks.
After looking at it again, I think that may be the problem, too. I guess the APP_USER is set when in the application builder and the Builder is running the report query as it is being parsed which is causing the error. I added a Begin - Exception block around that query and everything seems to work now.
Thanks again!

Stand-alone application generates error with function 'Ramp Pattern' (bug in application builder?)

Hello,
in my program a main.vi links to a sub-VI via 'open VI reference' and 'invoke node'. In this sub-VI the function 'Ramp Pattern' is used. The program itself runs normally, but if I build a stand-alone application using application builder I get an error message 'error 1003 occurred ..'. I believe this error is directly related to the build specifications which are as follows: the main.vi is referenced in a main build specification, the sub-VI in its own specification where the target is a LLB.
I appended an example-program that exhibits the error (when executing 'Application.exe' and pressing 'calculate ramp'). The error does not occur when disabling the 'ramp pattern' function and rebuilding the application.
I would rate this to be a bug in the application builder and would appreciate any help on how to solve this problem. However, due to the structure of the whole program the sub-VI has to remain in its own LLB.
Attachments:
RampPattern.zip ‏198 KB

There can be reasons why a VI might appear broken when loaded from an executable. For example, if you have different versions of the same VI or enum that differ in such a way as to break the calling VI, that can cause a broken arrow when loaded from the executable. If you have DLLs being called and the runtime engine can't find the DLL, that can cause a broken arrow that you might not see otherwise. Finally, there is a bug related to a VI appearing broken when its not.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Application Builder, Callback function and ActiveX

Similar Messages

Maybe you are looking for