Bill

Steve is correct. I just want to add that if they ever forget this
property, it is documented in comment right there at the top of the
CMQC.BAS file.

'*  This file can be used with either the WebSphere MQ server or the  *'
'*  WebSphere MQ client, depending on the conditional compilation     *'
'*  argument MqType:                                                  *'
'*                                                                    *'
'*  o   To set MqType:                                                *'
'*                                                                    *'
'*      1.  Select the menu option "Project - xx Properties" (where   *'
'*          xx is the name of the project).                           *'
'*      2.  On the tab labelled "Make", edit the field "Conditional   *'
'*          Compilation".                                             *'
'*                                                                    *'
'*  o   In the "Conditional Compiliation" field, enter (without the   *'
'*      quotes):                                                      *'
'*                                                                    *'
'*    "MqType = 1" for the WebSphere MQ server                        *'
'*    "MqType = 2" for the WebSphere MQ client                        *'
'*    "MqType = 3" for the WebSphere MQ extended transactional client *'
'*                                                                    *'
'*  The selection of client/server controls the selection of          *'
'*  WebSphere MQ DLL. The appropriate DLL must be installed and the   *'
'*  queue manager running for the Visual Basic application to         *'
'*  operate correctly.                                                *'
'*                                                                    *'
'*  COMMON PROBLEMS:                                                  *'
'*                                                                    *'
'*  ================================================                  *'
'*  Visual Basic error:                                               *'
'*  o   Run-time error '48': Error in loading DLL                     *'
'*  o   Run-time error '53': File not found                           *'
'*  ================================================                  *'
'*  PROBLEM:                                                          *'
'*  o   Incorrect Mqtype setting                                      *'
'*  SOLUTION:                                                         *'
'*  o   Change MqType setting -- see comments above                   *'

Rick



              "GIES, STEVE" <[EMAIL PROTECTED]>
                                                          To:                          
               [EMAIL PROTECTED]
              Sent by: MQSeries List                      cc:
              <[EMAIL PROTECTED]>                   Subject:   Re: VB client program 
preparation?



              Thursday February 26, 2004 04:56 PM
              Please respond to MQSeries List






Bill -

When using the standard MQI with VB, as opposed to the ActiveX classes,
you must indicate whether you want to compile with the server dll
(mqm.dll) or client dll (mqic32.dll).  You do this via a conditional
compilation variable.

Open up the project properties dialog box ( Project | {name} Properties
... }, click the Make tab, set the Conditional Compilation Arguments to
MqType = 2.  This will link with the client dll.  (To link with the
server dll, use MqType = 1). You do not need to have mqm.dll on your
server (either your development workstation or on the deployed server).

Hope this helps.

- Steve


-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of
Beinert, William
Sent: Thursday, February 26, 2004 1:31 PM
To: [EMAIL PROTECTED]
Subject: VB client program preparation?


I have a developer writing the first VB app to be run as a client. I
don't know VB at all, so I handed him the App. Prog. Guide and the
Client Guide. So this is what he tells me... Should he have an MQM.DLL?
What are we missing?

Thanks
Bill


Hi,
     I'm now testing my program code.  I copied all MQ-related
declaration from cmqb.bas module file that MQ Client installation gave
me.  It references a dll file which I cannot find in my workstation:
"MQM.DLL", why don't I have this or should I be using another dll?  All
MQI function calls makes reference to this dll, like:

  Declare Sub MQCONN Lib "MQM.DLL" Alias "[EMAIL PROTECTED]" _
    (ByVal QMgrName As String, _
           Hconn As Long, _
           CompCode As Long, _
           Reason As Long)

In the data definition file "CMQB.bas" that came with MQ Client, all MQI
functions are contained in "MQM.dll" file, which I didn't have.  Did I
miss anything in the installation?



Bill Beinert
Systems Programming
Con Edison

When they took the fourth amendment,
   I was quiet because I didn't deal drugs!
When they took the sixth amendment,
   I was quiet because, I was innocent.
When they took the second amendment,
   I was quiet because I didn't own a gun!
Now they've taken the first amendment,
   and I can say (or do) nothing about it.
The Second Amendment is in place in case they ignore the others. MODWN
DAbE

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
 Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Reply via email to