home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!news.u.washington.edu!gibdo!tvp
- From: tvp@gibdo.engr.washington.edu
- Newsgroups: comp.os.ms-windows.programmer.misc
- Subject: Problems calling a DLL function from a VB app. PLEASE HELP!
- Message-ID: <1992Dec15.135809.5339@u.washington.edu>
- Date: 15 Dec 92 13:58:09 GMT
- Article-I.D.: u.1992Dec15.135809.5339
- Sender: news@u.washington.edu (USENET News System)
- Organization: clearer than blir
- Lines: 28
-
-
- Okay, I posted a few days ago about not wanting the screen to blank
- for the few seconds it took me Shell() out to DOS to run an .exe
- utility (written in C) that I was calling from inside my VB app.
-
- I rewrote the inside of my C source to compile it into a .dll file.
- Then I followed the instructions in the VB manuals to declare and call
- the function inside the DLL that was replacing the standalone C app I
- used to use under DOS. But when I hit F5 to test the VB app, and get
- to the part where I push the command button that will cause the DLL
- function to be called, it fails and tells me:
-
- "Function or sub undefined"
-
- It also highlights the line where the function is called in the
- source. This is pretty maddening because the function IS defined
- right there in the Declarations section of the form. And it's defined
- correctly as far as I can tell too, it's of the proper type, with no
- mispellings in the Function name or the Lib path. Does anyone know
- what's up and how I can fix it? I'M STUCK!
-
- Thanks in advance to anyone who can help me.
-
- ------------------------------------------------------------------------
- Tad Perry Internet: tvp@gibdo.engr.washington.edu
- CompuServe: 70402,3020
- NIFTY-Serve: GBG01266
- ------------------------------------------------------------------------
-