To call a VB DLL.

It is possible to use a function from Visual Basic DLL. I created the DLL. But if i use the ORA_FFI package, its nt working. I used an example with no parameters. Please help...Maybe the ORA_FFI package works only with C DLL'S ....

Have you checked google?
First hit. Reply 17.

Similar Messages

How to auto-recognize the function parameters called from a DLL built by VC6.0

Hi,
I use Teststand 3.5 with C/C++ Adapter, and the DLL is built by VC6.0.
While I specify module for an action, the parameters of a function called from the DLL are not recognized.
Since I have the DLL source, I know I can select the source file and verify prototype in the "Source Code" Tab.
Under the way, almost parameters can be recognized, but some parameters, e.g. HANDLE or I definded, can not ( shows error message "The function definition cannot be found in the source file...").
How to recognise these parameters?
Thanks.

The problem isn't that TestStand doesn't have enough native types. A handle can be represented in a TestStand numeric variable just fine. Instead, the issue is that when you select Verify Prototype, TestStand doesn't fully pre process your headers and compile your code to determine the types. To do so would require TestStand not only to be a full C/C++ compiler but it would also have to be able to read your compiler's projects and settings to resolve include paths, macros, etc.
Since TestStand is not a C/C++ compiler, it just looks for the standard basic data types plus a few more that are common in test code. Other data types will not be automatically recognized even if they can be mapped to TestStand types.
Another option it to create a type library for your dll so that TestStand can automatically read the data type information from it. However, I don't know if that works for struct parameters and I looked for the document on devzone that explains how to do that in VC++ and it has been moved or deleted
Maybe an AE would know of a link to a current document that describes how to do this?

How can i avoid a pop-up window when calling the avi.dll?

Ok, here another try!
My problem is as followed:
My program calls the avi.dll to initialize, write into and close an
avi-file.
Now, when initializing it, a pop-up window is shown so you can choose the
codec to use.
My question is, can I pre-define the codec, so the pop-up window won't show
up?
The program is meant to write several files, some starting without the user
having to control them, so the pop-up window really isn't helping.
Any ideas?
I attached the avi.dll in case you need it to look at the problem.
Also helpful would be, if someone could tell me, how I can take a closer
look at the structure of the dll. Is there a program I can do that with?
Thanx!
regar
ds,
Martin

Hello Martin,
I have used this DLL before and wasn't asked to choose a codec. Maybe if you use all three functions (init, write, close), it works without problems. Here's a example that uses IMAQ hardware to acquire an 8-bit image at 30fps and writes each image to an avi file.
There are utilities to examine dlls (see what functions are exported and what the dependencies are, but you can't see source code since it is compiles.) Check out QuickView or DependencyWalker.
Attachments:
avigrab.zip ‏66 KB

Recupérer les valeur d'un Control via un .obj appelé depuis une DLL- Getting a Control value from an .obj file called from a dll

Bonjour,
Suite au passage à la version CVI 2013, il faut passer par un fichier .obj au lieu du .c quand on veut utiiser la LoadExternalModule.
Le pb qui en résulte impossibilité de récupérer la valeur des control dans l'uir géré par le .obj qui est appelé par une dll.
Autrement, il m'est impossible de faire parvenir à la dll les valeur des control ( dll qui appelle le .obj).
Quelqu'un a eu le même soucis amigos?
Merci
Hi,
When using the LoadExternalModule function in CVI 2013, we can no longer use a .c file. Instead we have to use an .obj file.
My issue is that' impossible for me to get a control value from an .iur managed by the .obj witchi is called by a dll.
Otherwise it's impossible for me to get the control vale when calling the .obj from a dll.
Any suggestions Amigos
Thanks

For people who could be interested in, here the code I provided to the customer. This code demonstrates that calling a function defined in a .obj file from a DLL which is called itself by a program can be realized without throwing any error.
In order to use this example, you will have to :
1) Open "main.cws"
2) Define "Madll" as Active Project (right clic on the project and click on "Set Active Project")
3) Build the DLL (CTRL+M)
4) Define "Main" as Active Project
5) Click on "Debug Project" in order to build the executable and run it
This example has been built with CVI 2013.
Jérémy C.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Travaux Pratiques d'initiation à LabVIEW et à la mesure
Du 2 au 23 octobre, partout en France
Attachments:
main.zip ‏70 KB

How to call a c++ dll from oracle

plz can someone help me how to call a c++ dll (not ocx coz 10g cant see ocx) from oracle 10g ?
Edited by: jihad jag on Apr 23, 2009 1:40 AM

I guess your request is timed out but to call shared libraries look for 'External Procedure Call' in Oracle documentation.

Calling a c++ dll that contains a dialog.

Hi,
I have a c++ dll that contains a dialog. When I try to display the dialog (ShowDialog(SW_SHOW);) the dialog is popped up but the dialog window is frozen and do not display its controls. The Java application is call an intermediate dll create by JNI that is calling the c++ dll.
Any Suggestions?
Thanks in advance,
Udi Raz

It should be discernable (by looking at the C# code) whether the C DLL needs to be registered.
If the DLL is serving COM objects it may need to be registered at a command-prompt with
regsvr32 <your_DLL_File_path>
If it's supplying .NET assemblies, I think it needs to be registered with
regasm <your_DLL_File_path>
Although I've written a few C DLLs, none were called from a C# DLL and I can't advise what subtle things to watch-out for in this scenario.
Do you have a way to validate/exercise the C DLL's functionality? Is it possible to through-together a C# application (not a C# DLL) that successfully uses the C DLL?
Luck/Cheers!
Message Edited by tbd on 12-03-2008 02:36 AM
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)

Can a call to a DLL be aborted?

Hi all,
I've got a rather huge project stat starts to cause bad problems now communicating with an USB device. There's a home-made DLL that calls some chip-specific DLL functions. From time to time a call that finally should simply close the handle to that device takes far too long, from seconds to hours. It will finally return and everything is done, but I cant affort to wait more than some few seconds.
Now my Q is, is there any way to abort a call to that DLL whenever it takes more than a specified period? I thought of dynamically call a VI that calls the DLL, but I am not sure if this would really help, as LV is really lazy when it hangs in the DLL call _now_! The system monitor shows no CPU usage (~1%) and does not show LV hanging, but LV does react to any clicks with long delayes, if at all. Would not like to set that up just to find out that it could not have worked.
Any C programme here that has an idea to change the home-made dll?
Greetings from Germany!
Uwe

After re-thinking the whole thing, I conclude this is impossibel, at least in the way I asked for.
To abort a process, it must be a separate process. As LabVIEW itself is a single process, I would have to bring this DLL-stuff into another process, which could just be another LV runtime engine. This might work in the devellopment system, but no way when compiling the main app into an exe itself. OR I had to use an older runtime engine.
AND, I would need to create a LabVIEW daemon that accepts the jobs with the DLL as it needs to stay in memory when being active.
AND I'd need a whole bunch of communication between both processes, exchanging different data like handles, errors, commands and communication packets.
Conclusion: I will not try going this way unless someone proofs me wrong.
Greetings from Germany!
Uwe

Has anyone called the Solver dll in Labview?

I have developed a non-linear mathematical model in Excel that uses it's Solver routine. I am currently trying to convert this over into the Labview environment because the equations are more manageable and the front panel interface is more marketable. However, I need the power of the Solver dll.
Frontline Systems (www.solver.com) provides an evaluation version of the dll but I am new to this and I was wondering if anyone has done it and could provide a VI which calls this dll or has any suggestions, please?
I think it would be pretty nifty if Labview could provide this sort of optimisation power. (It's current optimisation routines in the Mathematics toolbox are pretty limited and are not nearly as powerful as Solver)
. But I'm sure a labview guru could configure a simple VI which calls the Solver dll for a multi-dimensional non-linear problems similar to Excel....
Many thanks in anticipation!!!

Hello �
You might want to consider using a Call Library Function Node. This node supports a large number of data types and calling conventions. You can use it to call functions in most standard and custom-made DLLs and shared libraries.
Refer to the Configuring the Call Library Function Node section of Chapter 2, Shared Libraries (DLLs), of the Using External Code in LabVIEW manual (attached) for more information about using the Call Library Node to call code from text-based programming languages.
Hope this helps!
S Vences
Applications Engineer
National Instruments
Attachments:
Call_Library_Function.pdf ‏2030 KB

Calling LV created DLL from LV

Howdy-
I'm trying to call a LV DLL from within LV (seperate project). Once the DLL has been comppiled I'm using the Import Shared Library to create the node.
However when I try this I get an error message with the import that appears to have trouble with LVBoolean and int32_t.
I've created a simple DLL (adds a DBL to an INT 32 and creates a Bool when the sum is > 0).
Compiling this DLL and trying to import it has the same issue.
Any clues?
Attachments:
Import Shared Lib.png ‏49 KB
My DLL.zip ‏34 KB

nathand wrote:
This does mean LabVIEW will create the datatypes with U8 instead of booleans, which you can replace yourself with a boolean after importing.
Except that the Call Library Node doesn't allow for configuration of an explicit boolean type (for obvious reasons as there is no standardized boolean datatype in C before C11 and even then the standard says nothing about if it should be a byte or the prefered integer size for the current platform or anything else). LabVIEW then uses Adapt to Type instead, which forces the skalar parameter to be always passed by pointer!
Most simple solution is to still use an explicit integer that is properly sized and convert between the LV Boolean and the integer on the diagram.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How to call LabVIEW ActiveX dlls into VB6

I'm jumping in on a project written primarily in VB6. I'd much rather wirte code in LabVIEW so what I am looking for is some example code for calling LabVIEW activeX dlls into VB6. Does anyone have example code? I need to see how the LabVIEW libraries and classes are called and used in VB6.

Hi Drewdafis,
Refer to this link for example code on calling a LabVIEW DLL from Visual Basic.
Hope this helps!
Best Regards,
Jonathan N.
National Instruments

Calling a VC++ DLL from a java code!!!! Urgent!!!

Hi,
I need a Java code which will call a VC++ dll .(similarly the viceversa also.....from vc++ calling a java application)
If any one have the code Please send it...
Thankx,
Donam.

There is also some details in here which might save you some of the hassle I had.
http://forum.java.sun.com/thread.jsp?forum=52&thread=210212

Help needed calling GetVolumeInformationW, kernel32.dll

Hello,
I'm trying to get the file system of disks using the GetVolumeInformation function. I got it to work using the ANSI version, but now need to use the unicode version. I can't get a sensible response from the unicode version ( I get what look like chinese characters or it crashes). I'm new to c++ and JNI. I've tried variations of (*env).NewString(szFileSystemNameBuffer, strlen(szFileSystemNameBuffer)) and (*env).NewStringUTF(szFileSystemNameBuffer) but no joy. The closest I've come is when I got back "N" from the call, thought this may have been the start of "NTFS" and I didn't have enough space for the rest.
JNIEXPORT jstring JNICALL Java_com_nortel_cc_dsf_utils_systeminfo_JniConfigDetail_getFileSystem(JNIEnv *env, jclass obj, jchar path) {
      CHAR szDrive[4];
      szDrive[0] = path;
      szDrive[1] = ':';
      szDrive[2] = '\\';
      szDrive[3] = '\0';
      CHAR szVolumeNameBuffer[12]; //this will have the name of your drive
      DWORD dwVolumeSerialNumber; //this will have the serial number of your drive
      DWORD dwMaximumComponentLength; //this is the max length in between each \ in a path
      DWORD dwFileSystemFlags; //this will return flags about the drive's file system
      CHAR szFileSystemNameBuffer[10]; //this will contain the type of file system (ex: NTFS)
      //make call to kernell32.dll
      BOOL result = GetVolumeInformationW((LPCWSTR)szDrive, (LPWSTR)szVolumeNameBuffer, 12, &dwVolumeSerialNumber, &dwMaximumComponentLength, &dwFileSystemFlags, (LPWSTR)szFileSystemNameBuffer, 10);
return env->NewString((jchar *)szFileSystemNameBuffer, strlen(szFileSystemNameBuffer));Can anyone shed any light on what I need to do to get back the file system?
Thanks
Tom

Here's what I have in the function.
JNIEXPORT jstring JNICALL Java_JniConfigDetail_getFileSystem(JNIEnv *env, jclass obj, jchar path) {
      WCHAR szDrive[4];
      szDrive[0] = path;
      szDrive[1] = ':';
      szDrive[2] = '\\';
      szDrive[3] = '\0';
      CHAR szVolumeNameBuffer[10]; //this will have the name of your drive
      DWORD dwVolumeSerialNumber; //this will have the serial number of your drive
      DWORD dwMaximumComponentLength; //this is the max length in between each \ in a path
      DWORD dwFileSystemFlags; //this will return flags about the drive's file system
      WCHAR szFileSystemNameBuffer[12]; //this will contain the type of file system (ex: NTFS)
      //make call to kernell32.dll
      BOOL result = GetVolumeInformationW((LPCWSTR)szDrive, (LPWSTR)szVolumeNameBuffer, 12, &dwVolumeSerialNumber, &dwMaximumComponentLength, &dwFileSystemFlags, (LPWSTR)szFileSystemNameBuffer, 10);
      if (result) {
           if (szFileSystemNameBuffer[0] == 'N' &&
               szFileSystemNameBuffer[1] == 'T' &&
               szFileSystemNameBuffer[2] == 'F' &&
               szFileSystemNameBuffer[3] == 'S') {
               return (*env).NewString(szFileSystemNameBuffer, strlen(szFileSystemNameBuffer));
      return (*env).NewStringUTF("null");
}And here are the errors the above function causes.
Errors:
1>ConfigDetail.cpp
1>..\..\ConfigDetail\ConfigDetail\ConfigDetail.cpp(61) : error C2664: 'strlen' : cannot convert parameter 1 from 'WCHAR [12]' to 'const char *'
1> Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
1>..\..\ConfigDetail\ConfigDetail\ConfigDetail.cpp(61) : error C2664: 'JNIEnv_::NewString' : cannot convert parameter 1 from 'WCHAR [12]' to 'const jchar *'
1> Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
After looking more closely at the errors, I tried the reinterpret cast like so.
return (*env).NewString(reinterpret_cast <const jchar*>(szFileSystemNameBuffer), strlen(reinterpret_cast <const char*>(szFileSystemNameBuffer)));This returns me "N" only. So the question remains how do I get the full "NTFS" which we now know is being returned.

Calling Borland C++ DLL

want to call my borland c++ 5 or 6 generated DLL, is it possible ?
any samples or steps I can follow ?
thanks.

Richard Zhu wrote:
> want to call my borland c++ 5 or 6 generated DLL, is it possible ?
>
> any samples or steps I can follow ?
There shouldn't be any specific problem with calling Borland compiled
DLLs with the Call Library Node in LabVIEW, provided the DLL is
installed properly with all necessary Borland runtime DLLs on the target
system.
As to examples check out the examples/dll directory in LabVIEW. DLLs are
supposed to be a standard format and it should not make any difference
if they are created with Visual Studio, Borland C or even gcc.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Calling 64-bit dll from labview 8.2 on Windows7

Hello,
I have tried the LABview driver from the OMNIDRIVER (OceanOptics) package. But when calling functions from the “OmniDriver32.dll” , LABView is crashing and says that the memory is corrupted.
I am using LABVIEW 8.2 (32-bit) running on Windows 7 (64-bit). I have tried some LABView code examples given for LABview 7.1 and 8.0. These example are using the OmniDriver32.dll (not the OmniDriver64.dll).
But maybe these example are assuming that you are on a 32-bit operating system, which is not my case.
So I have tried calling the OmniDriver64.dll. but LABView seems not to recognised the dll and can’t read the included functions.
Is there a way to call some 64-bit dll from LABview 8.2 ?
Or do I need to buy a new license for LABVIEW 64-bit ?
Thanks,
Pierre

There is no virtualization support for DLL bitness issues outside of the Windows standard directories. The Windows and System directories that an application "sees" depends on its bitness. All other directories are not mapped depending on the calling process' bitness.
So if you have installed 32 Bit LabVIEW and are not calling one of the system DLLs, you have to point the path of the DLL to the real 32 bit DLL. Pointing it to a 64 bit DLL should not even be able to get the VI compilable, since Windows will refuse to load the DLL into the 32 bit process as being an unknown file format, and that should make the VI broken.
If you need to call a system DLL you simply enter the DLL name without path and Windows will find the according DLL for LabVIEW.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Calling a C# DLL in Labview that makes a call to another DLL

I have a set of DLLs created with C# that I am calling in Labview. They all work fine using the .NET functions except for one DLL that makes a call to another DLL created in C. It returns an error. Any ideas why this wouldn't work? All DLLs are located in the same Windows directory.

It should be discernable (by looking at the C# code) whether the C DLL needs to be registered.
If the DLL is serving COM objects it may need to be registered at a command-prompt with
regsvr32 <your_DLL_File_path>
If it's supplying .NET assemblies, I think it needs to be registered with
regasm <your_DLL_File_path>
Although I've written a few C DLLs, none were called from a C# DLL and I can't advise what subtle things to watch-out for in this scenario.
Do you have a way to validate/exercise the C DLL's functionality? Is it possible to through-together a C# application (not a C# DLL) that successfully uses the C DLL?
Luck/Cheers!
Message Edited by tbd on 12-03-2008 02:36 AM
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)

To call a VB dll from java

Hi,
I want to know how one can call a VB dll from Java.I know it is something like calling a C dll which in turn calls the VB dll.I also went through the tutorial provided on the sun site and was able to call a C dll through java but I still do not know how to call a VB dll from java.
regards,
Anshuman

Have you checked google?
First hit. Reply 17.

To call a VB DLL.

Similar Messages

Maybe you are looking for