EB>

EB>After two days of playing with this, I finally figured out
  >a way to do it.  Instead of using the names of the
  >functions, I used ordinals  such as :

EB>ReadPort {at}1

EB>However, I also had to edit the .DEF file Guidelines
  >created.  Is there any way around this?  Is there another
  >way to get Guidelines to recognize it?  A different way of
  >handling the DLL in the first place?  Any help would be
  >appreciated.

Ok, I just wrote a reply to your other note and I described how to
handle .OBJ files (-=AS YOUR SUBJECT LINE SPECIFIED=-).  Now DLLs are
just as easy.  If you don't want to be forced to export your functions
via the DEF file (and you are using Borland C++) then simply add
_export to your function definition (not declaration)--in your C++ file
not your .H file.

ie.

my.h file
char myFunc(char This,int That);

my.cpp file
char _export myFunc(char This,int That);

Then it should export it correctly.  Use the method I described in the
previous message except instead of adding the OBJ file, add the LIB
file.  (Or you could load the functions run-time, but that's another
story.)

Michael Douglass
___
 .Mike's Mail Internet:   MICHAEL.DOUGLASS{at}LCHANCE.SAT.TX.US

--- Maximus/2 2.01wb