forum.vdsworld.com

kc7aad · Posted: Fri Oct 28, 2005 9:17 pm Post subject: Newb trying DLL's now!! AHHHH!!

OK.. So i am trying to lear as i go, and am trying to figure out DLL's. I tied to put one in a simple program, and when I try and run it, it comes up in the compiler, as an error for line 2, which is:
EXTERNAL VDSUG.DLL

Is this the right format?? I tried putting it in the directory i loaded it into, I also tried putting it in the SYSTEM32 folder, and still have no luck!!

Anyone offer assistance to someone who feels like shooting the computer??

Thanks

Tdk161 · Posted: Fri Oct 28, 2005 10:40 pm Post subject:

Hi

what OS you are using?

ShinobiSoft · Posted: Sat Oct 29, 2005 3:25 pm Post subject:

if you are using VDS 5, you need to define the command and function
names first. For example,

Serge · Posted: Sun Oct 30, 2005 1:41 am Post subject:

before using the EXTERNAL VDSUG.DLL line, i suggest you use DIRECTORY CHANGE, @PATH(%0) so that it reads,

- for vds 5

webdaddy · Posted: Fri Nov 04, 2005 9:41 pm Post subject: Um im loosing it

You mean to tell me that you need to tell the application what directory its running in. Cant you just append @path(%0) in front of the files you are calling as well? Sorry I may be going stupid on ya....hehe

Just asking because I have never done that at the begining of a script.

ShinobiSoft · Posted: Fri Nov 04, 2005 10:03 pm Post subject:

Actually, both ways are appropriate, along with copying them, the dlls, to the
Windows\System folder.

I've noticed a problem with VDS, every once in awhile, VDS doesn't
always change the current directory to the path of the script that it just
opened in the IDE. (I've only noticed this for VDS 4). One surefire way is to
of course issue the DIRECTORY CHANGE,@PATH(%0) command before trying
to load any external dlls.

As for myself, I always specify the full path to the extension(s) that I intend
to use in my scripts.