Re: Tools for make menus on FJ Powercobol.




"Massimo" <blue_max_53@xxxxxxxxxxx> wrote in message
news:EuKeg.17485$cX1.271130@xxxxxxxxxxxxxxxxxxxxx
For my applications in FJ Powercobol, I have make the menu with the tools
for menu of FJ Powercobol.
I don't think both the best solution.
Who a best solution suggests me?
Best regards.
Massimo from Rome.


PowerCOBOL is a very useful "QuickBuild" GUI system for creating Windows
applications quickly. The Menus are very good and so are the other controls
that are packaged with it. It is particularly adept at building ActiveX and
COM components and I still use it for this, although it is some time since I
built a commercial application with it. (Applications I have built with it
in the past have proven to be stable and users are happy; I think it is (or
was...perhaps) a good product.

However, some people are concerned about compatibility with future Windows
environments, and there have been rumours that Fujitsu may not support it in
the future. (These rumours have not been confirmed or denied by the
company).

What are your alternatives?

These will depend on what you are building with it

You could move to a web enabled application, or you could use Delphi or
other Windows development system instead. You could look at .NET with Visual
Studio and this allows you to write in C#, VB, C++, or COBOL, but Fujitsu's
COBOL for .NET is very expensive.

It really depends on how committed you are to using COBOL.

Java is free and fun to use; the web (ASP, HTML, XML etc) is even more fun.

If you are determined to do it in COBOL there is really nothing wrong with
PowerCOBOL. If you don't like the controls that come with it, use a
different set, like MicroSoft Foundation Classes, or perhaps some third
party offerings. FlexiSoft have COM controls that are compatible with
PowerCOBOL. Check out:
http://www.devdirect.com/ALL/UserInterfaceComponents_SGROUP_0004.aspx

Your cheapest option is to stay with what you've got and simply get to know
it better... :-)

Pete.


.



Relevant Pages

  • Re: PowerCOBOL conversion to DotNET
    ... COBOL from the seventies, which have been converted and migrated ... Presentation layer. ... comes to platform change. ... I think it was a major oversight in PowerCOBOL. ...
    (comp.lang.cobol)
  • Re: Treeviews
    ... Neither PowerCOBOL nor NETCobol have ever "excluded collections". ... Java and OO COBOL. ... WebintMT AS "WebintMT". ... Now block the constructed record into the output buffer... ...
    (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: Passing values to PowerCOBOL DLL
    ... simple as adding a LINKAGE section and PROCEDURE DIVISION USING clause to the PowerCOBOL DLL. ... I've had that working in the past but wanted to use the OLE control approach instead. ... I had already tried adding a "custom property" named CustID to the form, which was visible in VB and I could set to a value within VB but seemed unable to reference it within COBOL. ... and the new owner brought back the old timer who resurrected the old COBOL code and got it working on the new platform. ...
    (comp.lang.cobol)
  • Re: [experiences] Fujitsu NetCOBOL for .NET
    ... >> possible to work with COBOL data files ... >> provided by fujitsu? ... They have no migration tool to move from PowerCOBOL to NET ... both NetCOBOL and PowerCOBOL is nothing less than abysmal. ...
    (comp.lang.cobol)