Re: Thoughts on passing values to PowerCOBOL DLL

Michael Russell wrote:

I don't know much about that M$ stuff, nor PowerCobol, but this conversation you two just had made me think "What nice posts."

That's 'nice' as in written well, courteous & helpful. Great stuff, if you don't mind my saying so.

Regards
Michael

Thank you Michael. Your comments are very much appreciated. Perhaps too often a call for help meets with remarks such as "do your own homework" (okay, sometimes it's justified).

I'm guessing that most of us here are seasoned COBOL programmers, that is, probably 50 years of age or older, with a few younger readers who have had COBOL thrust upon them. At my age I sometimes have trouble finding my eyeglasses, which I'm wearing! In such cases it's 'nice' to have an objective pair of eyes to help guide us.

In this case, it turned out that the problem was indeed "something simple I've overlooked". Even when a module has only a single object, and that object has only a single property, then that property must be referenced explicitly.

If we were speaking of programs and variables (which these in fact are) then this would be a matter of "uniqueness of reference", which in COBOL means that a fully qualified reference need only be specified when necessary to avoid ambiguity.

But this isn't COBOL, it's object oriented programming.
Perhaps some things *are* better done by committee.


There's probably something simple that I've overlooked, but it's not obvious to me how to pass a value to a PowerCOBOL DLL called from VB.

What I eventually discovered was that reference to CustID had to be *explicit* in the form "CustID of Control1", even though the project has only one form and only one control. After that everything fell into place.

.

Relevant Pages

  • Re: CALL using OMITTED
    ... look for ways that Cobol can help with this. ... invoke MyCollection "new" returning CollectionObject ... I've never done it so I don't know the full implications - hopefully it creates a unique reference in the first Collection without impacting the second. ... Procedure Div using.... ...
    (comp.lang.cobol)
  • Re: ouvrir un document word =?ISO-8859-1?Q?=E0_partir_d=27un?= =?ISO-8859-1?Q?_progr
    ... The trouble is, there are so many permutations and in the case of mail-merge, MS let's you even do "IF tests ..." ... You database is it a COBOL ISAM or a DB Table you were getting your address info from. ... It appears if you have an ODBC Driver then for mail-merge, MS Word can reference your DB. ... the meeting will be held at << a merged field>> and the date and time of the meeting is << a merged field ...
    (comp.lang.cobol)
  • Re: invoking a method
    ... The use of SET as shown here, will not work outside the Fujitsu Object COBOL ... invoke DBObject ... I will admit I have not worked on anyone else's Cobol compiler so I ... typical reference manual for a Cobol Compiler will have line and box based ...
    (comp.lang.cobol)
  • Re: Thoughts on passing values to PowerCOBOL DLL
    ... COBOL thrust upon them. ... At my age I sometimes have trouble finding my ... then this would be a matter of "uniqueness of reference", ... I think as you become more familiar with it (even through use of PowerCOBOL) ...
    (comp.lang.cobol)
  • Re: Help Constructing Fictional Cross-Religious Movement
    ... >>Wilson Heydt wrote: ... Except that in COBOL ... reference to it) in some variable/array/objectMember. ... in languages which are designed to support OO. ...
    (rec.arts.sf.composition)