Chris, Essentially, what you have to do is to provide an entry point to the DLL that returns the information about the functions and their parameters. When I code a DLL, I generally provide one entry point that returns the version information about the DLL and another that returns information about the rest of the entry points and their parameters. It is somewhat complicated to provide via email . . . there are whole chapters on the subject in Mastering Delphi books.
At 05:05 AM 10/12/2007, you wrote: >Hello list, > >I have a financial package that exports functions (via 2 .DLL's) to >crystal reports. I have a list of all the functions, parameters and >return types, so I can use them in my own projects. > >When I use the dll's, I have to declare all the functions - no problem, >I own them, I've got the info. > >When crystal uses them, all I have to do is put the dll's in the same >folder as the main crystal executable -voila! the functions are >available, remove the dll's and the functions disappear. > >Over the years, the financial package has been patched and upgraded, and >the quantity of functions has increased, again, no problem, drop the new >dll into crystals folder, and I can see the new functions. > >There is no inf file, just the dll's > >I want to do this, I want to be able to code a project that reads a dll >(any dll), extracts the function names, parameters and return types and >exposes them to the user. > >Can a guru show me the way? > >Cheers - Chris > >_______________________________________________ >Delphi mailing list -> [email protected] >http://www.elists.org/mailman/listinfo/delphi Ralph D. Wilson II Systems Analyst Home: (210) 497-2643 Cell: (210) 387-7744 Fax: (210) 497-5726 [EMAIL PROTECTED] [EMAIL PROTECTED] _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
