Details | Last modification | View Log | RSS feed
Rev | Author | Line No. | Line |
---|---|---|---|
284 | f9daq | 1 | Sample of using USMCDLL.dll library with MS Visual Basic 6.0 |
2 | |||
3 | Files: |
||
4 | |||
5 | DLGForm.frm - main dialog |
||
6 | DLGForm.frx - |
||
7 | Project1.vbw - project file |
||
8 | Dialog.frm - start dialog where dll is inited and devices are enumerated |
||
9 | Module1.bas - module file with dll function declarations and sample MsgBox output functions |
||
10 | Project1.vbp - project file |
||
11 | OUTPUT\USMCVBDLL.dll - Interface DLL to connect VB 6.0 program to standard DLL |
||
12 | OUTPUT\USMCVBTest.exe - VB 6.0 Output exe program |
||
13 | OUTPUT\uSMC Library.dll - Dev. Kit file (connected to NI VISA) |
||
14 | OUTPUT\USMCDLL.dll - USMCDLL.dll |
||
15 | |||
16 | Notes: |
||
17 | Sample can be used to start with writing your own applications controlling uSMC devices. |
||
18 | 0) Contents of "output" directory should be placed to installation directory of SMCVieW. |
||
19 | 1) IMPORTANT Visual Basic 6.0 does not close dll files used when it's debugger (interpretator) |
||
20 | running, so when you start debugging more then once it can't find any connected controllers. |
||
21 | To work properly it (Visual Basic) must be restarted any time you finish debugging. |
||
22 | There are no such problems when you start created exe file. |
||
23 | 2) IMPORTANT Other problem is that Visual Basic does not search for dll in current directory, |
||
24 | so to run debugger you should copy USMCDLL.dll, uSMC Library.dll and USMCVBDLL.dll in |
||
25 | @win@\System32\ directory. There is no such problem when running exe file, when you placed it in directory where dlls are. |