MF Dialog System, how to use
Quote:
>>We are about to start using MFCobol as a client based tool. There are
>>two options 1) Have the Cobol program start first, it then calls Dialog
>>System or 2) have Dialog fire up first and have it do the callouts to the
>>Cobol program.
>>Is there a 'best' way? Can you relate your experiences using DS?
>>Thanks!!
>Hi,
>Well I guess there is no 'best' way but these are the guidelines that
>I and customers that I have talked to have followed in the past and
>they seem to work.
>For a demo/simple prototype get cobol to call dsrun. for any other
>projects use dsmgr.
>dsmgr allows you to split your interface up into multiple screensets
>and programs. This has the obvious benefits of modularising the
>project and making it easier to assign bits out in teams.
I think Graham means dsrunner here (not dsmgr). As he says, there is no
best way, it all depends on your application.
However, for applications involving multiple screensets, I would
definitely recommend use of dsrunner, as it will automate most of the
work involve in switching between screensets.
There is one other big advantage in using CALLOUTs, in that you can run
the CALLOUTs from within the definition software. This obviously makes
prototyping somewhat easier.
