🚀 go-pugleaf

Thanks very much, Gambit.

I'll use Automation or RPC, as you recommend.

The exported function uses some objects with C++Builder language extensions 
(e.g., "__published") which are off-limits to the other application.  These 
objects are also used elsewhere in the exporting application, so I felt the 
best way to let both applications link to the same function is to export the 
critical function from that application.

Thanks for pointing me to Automation and RPC.

Regards.
Greg

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:42267292@newsgroups.borland.com...
>
> "Greg Bullock" <greg dot bullock at atk dot com> wrote in message
> news:4226686a$1@newsgroups.borland.com...
>
>> AppOne exports a function declared as follows:
>>
>> TMyStruct __stdcall __declspec(dllimport) GetMyStruct(
>>           const char *StrA,
>>           const char *StrB,
>>           const SYSTEMTIME& DateTime);
>
> That is not an export.  That is an import.
>
>> AppTwo attempts to call this function using code something
>> like the following:
>
> I do not suggest you do it that way.  Why do you need applications to call
> each other's functions in the first place?  That is not a very good 
> design.
> Shared code should be placed into a DLL instead.  Otherwise, you should 
> use
> Automation or RPC to allow applications to call each others functions in a
> safe manner.
>
>
> Gambit
>
>