I have, but it's an app I inherited and it's using an in-house written
..dll to simplify the process - I can't provide the .dll to anyone
outside the company though. I did a little investigation when we started
talking about using MQ. The local client is provided as a set of .dll's;
it looked like you should be able to access one using the standard
Paradox .dll process. There was also an ActiveX available that may
simplify the programming some.
Ed Nash wrote:
Quote:
I'm looking for any experience and knowledge on this. My idea is to
send a data string to mainframe which will validate some of the data in
the string and send a repsonse back to the PC. We already have the
backend process (mainframe sees message in its queue and acts on it) in
place from another client-server app so I don't need to invent that. I
just need to have Paradox interact with the local MQ Client for Windows. |