COBOL and VB6

Thread View: comp.lang.basic.visual.3rdparty

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by awoa Thu, 27 Jul 2000 00:00

#56

Author: awoa
Date: Thu, 27 Jul 2000 00:00

12 lines
1456 bytes

I want to pass data between a VB6 front and a COBOL dll back.  Can anyone
tell me what I'm looking at here?  Can VB6 find the entry point in any COBOL
dll?  Does it depend on the COBOL compiler?  Is there a particular COBOL
product (compiler) that works better with VB6? i.e. Microfocus; CA
Realia......  Are there runtime files involved?  License and or Royalty
issues with distribution?

I'm still searching sites for this information.......they just don't seem to
have the content needed to answer these questions.

Thanks
Art

Re: COBOL and VB6

#57

Author: Craig Powers
Date: Thu, 27 Jul 2000 00:00

13 lines
1725 bytes

awoa wrote:
> 
> I want to pass data between a VB6 front and a COBOL dll back.  Can anyone
> tell me what I'm looking at here?  Can VB6 find the entry point in any COBOL
> dll?  Does it depend on the COBOL compiler?

It depends on the compiler -- VB can handle two types of DLLs, ActiveX
DLLs and plain Win32 DLLs.  VB expects exports from Win32 DLLs to use
the stdcall calling convention, and aside from that requirement the only
other thing you would have to worry about would be interaction of
argument types (figuring out what is equivalent in the two languages).
I have zero COBOL experience, so I can't speculate as to any likely
issues in that regard.

Re: COBOL and VB6

#58

Author: Ray Smith
Date: Fri, 28 Jul 2000 00:00

38 lines
2402 bytes

I just read another response to you message that mentioned AcuCobol, which
is what we use here.

Using AcuODBC you can setup ODBC sources in Windows for AcuCobol files which
seems
to work reasonable, if a little slow. (as a side note I have heard a
complete re-write of AcuODBC
is underway and these speed issues will be resolved.)

Just this week a have been testing calling Cobol program from VB using COM
and it works great.
Just create an object, point to the program and run it, passing/receiving
whatever parameters you like.

AcuODBC is an add on package and is required to be purchased seperately.
AcuCobol has runtime fies and runtime licenses.  I "beleive" the runtime
fees are reasonable but don't know the exact prices.

Ray Smith

awoa <awoa@email.msn.com> wrote in message
news:u07X6f49$GA.328@cpmsnbbsa08...
> I want to pass data between a VB6 front and a COBOL dll back.  Can anyone
> tell me what I'm looking at here?  Can VB6 find the entry point in any
COBOL
> dll?  Does it depend on the COBOL compiler?  Is there a particular COBOL
> product (compiler) that works better with VB6? i.e. Microfocus; CA
> Realia......  Are there runtime files involved?  License and or Royalty
> issues with distribution?
>
> I'm still searching sites for this information.......they just don't seem
to
> have the content needed to answer these questions.
>
> Thanks
> Art
>
>

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads