Fujitsu NetCOBOL for .NET and Visual Basic 6

Does anyone have a sample of how to use Fujitsu NetCOBOL for .NET to
call a Visual Basic 6 DLL?

Glen Groves wrote:
> Does anyone have a sample of how to use Fujitsu NetCOBOL for .NET to
> call a Visual Basic 6 DLL?

Doesn't Fujitsu have oodles of examples in their documentation?

On Wed, 4 Oct 2006 07:37:57 -0500, "HeyBub" <heybubNOSPAM@gmail.com>
wrote:

>Glen Groves wrote: 
>
>Doesn't Fujitsu have oodles of examples in their documentation?
>
Fujitsu has a lot of samples but none specific to this application.
Using the platform invocation services it doesn't recognize the VB6
entry point. For that matter, I don't know if it even recognizes the
fact that it is a valid DLL. If I rename a text file to Text.dll and
try yto call it I get the same entry point error.

Glen Groves wrote:
> On Wed, 4 Oct 2006 07:37:57 -0500, "HeyBub" <heybubNOSPAM@gmail.com>
> wrote:
> 
> Fujitsu has a lot of samples but none specific to this application.
> Using the platform invocation services it doesn't recognize the VB6
> entry point. For that matter, I don't know if it even recognizes the
> fact that it is a valid DLL. If I rename a text file to Text.dll and
> try yto call it I get the same entry point error.
U compile it with DYNAMIC proram structure, or not?
to be sure that all right, disable DYNAMIC program structure, include
into fujitsu project LIB file generated by VB with DLL, don't forget
describe right calling and passing data convention "Chapter 10. Calling
Subprograms (Inter- Program Communication)" of NetCOBOL User Guide. If
all seems right but u still get link error, check is you need specify
NOALPHAL compiler option.

On 8 Oct 2006 14:08:57 -0700, "ski" <t4na5nb02@sneakemail.com> wrote:

>
>Glen Groves wrote: 
>U compile it with DYNAMIC proram structure, or not?
>to be sure that all right, disable DYNAMIC program structure, include
>into fujitsu project LIB file generated by VB with DLL, don't forget
>describe right calling and passing data convention "Chapter 10. Calling
>Subprograms (Inter- Program Communication)" of NetCOBOL User Guide. If
>all seems right but u still get link error, check is you need specify
>NOALPHAL compiler option.

Thanks for the input. I'll check it out. I'm also calling a C++
program from Fujitsu NetCOBOL for .NET and having a much easier time
with it.