I gave that a try and here are the results;

....
17. RECEIVING CALENDAR
18. RECEIVING CALENDAR SMITHFIELD
19. START WINTEGRATE

Which would you like? ( 1 - 19 )  ?19
Enter  ?  for help
wIntegrate Command >SCRIPT 'QUERY\QUERY.WIS'
wIntegrate Command >IS'
Press any key to return to the menu...


By the way the WIN.COMLINE compiles with warnings right 'out of the box' -
missing final end statement.  I applied the changes as you suggested and it
didn't compile at all.  So, I just did this;


0159: 3000  IF CMND = "WIN.SERVER" THEN
0160:          CALL @EXECSUB("WIN.SERVER",'','')
0161:       END ELSE

Just to make it easy to check it out.  No such luck

Thanks
Anthony

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ian Renfrew
Sent: Wednesday, December 15, 2004 2:55 PM
To: [EMAIL PROTECTED]
Subject: RE: [U2] wIntegrate (on Universe) Question

You can try this:

Create a test program and insert the following three lines:

DATA "SCRIPT 'QUERY\QUERY.WIS'": @AM
EXECUTE "WIN.COMLINE"
STOP

Compile and catalog test program.

Modify program WIN.COMLINE (usually found in WIN.PROGS file). Locate and
modify the lines:

* Run a script
* At this point, we are assuming that the user input was either a
* script statement, such as:   Set Title "This is a window title"
* a script ID, as held in the file WIN.SCRIPT.
* or WIN.TRANSFER sent from the PC as a file transfer has been run.
*
3000  IF CMND = "WIN.TRANSFER" THEN
         CALL @EXECSUB("WIN.TRANSFER",'','')
      END ELSE
         IF SCRIPT.FILE AND LEN(CMND) < 100 THEN
            READ DUM FROM F.SCRIPT, CMND THEN ;* Did the user enter a script
ID?
               CMND = DUM ;* Yes and its now in variable CMND
            END
         END
*
         IF COUNT(CMND,AM) THEN
            CALL WIN.HSCRIPTC(CMND)
         END ELSE
            CALL WIN.COMSUB(CMND)
         END
*
END
         RETURN
* Run a script
* At this point, we are assuming that the user input was either a
* script statement, such as:   Set Title "This is a window title"
* a script ID, as held in the file WIN.SCRIPT.
* or WIN.TRANSFER sent from the PC as a file transfer has been run.
*
3000  IF CMND = "WIN.TRANSFER" THEN
         CALL @EXECSUB("WIN.TRANSFER",'','')
      END ELSE
         IF CMND = "WIN.SERVER" THEN
            CALL @EXECSUB("WIN.SERVER",'','')
         END ELSE
         IF SCRIPT.FILE AND LEN(CMND) < 100 THEN
            READ DUM FROM F.SCRIPT, CMND THEN ;* Did the user enter a script
ID?
               CMND = DUM ;* Yes and its now in variable CMND
            END
         END
*
         IF COUNT(CMND,AM) THEN
            CALL WIN.HSCRIPTC(CMND)
         END ELSE
            CALL WIN.COMSUB(CMND)
         END
*
END
END
         RETURN

Essentially you're adding the ability to call the routine WIN.SERVER.

>From your menu, you should be able to execute the test program.

Regards,  Ian Renfrew

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anthony Dzikiewicz
Sent: Wednesday, December 15, 2004 12:06 PM
To: [EMAIL PROTECTED]
Subject: [U2] wIntegrate (on Universe) Question

I forget if there is a separate group for this product.  If so, sorry.
However, my problem is this;

I am evaluating the wIntegrate product.  One of the uses that we have for
this is the query builder/report viewer.  We have a person who used to
tinker at the command line.  We have long since pulled the plug on this kind
of thing, because they did some 'bad things'.  However, it is nice to let
them have the ability to query the data (after all it is theirs).  So, it
seems wIntegrate can do this for us.  My problem is that you need to be at a
command line to allow wIntegrate to operate.  So, we're back to square one -
user at the command line.

Our system is based on standard Universe menus.  Is there a way to add a
menu option (or create a VOC) that will allow the user to 'mess' with query
builder, etc  ?  I have tried adding WIN.SERVER as a menu option.  However,
this half works.  I created a simple query and tried to put it to the report
writer and it times out, because the WIN.SERVER closes.  If I send it to the
screen, it works ok.

Any workarounds to this ?

Anthony
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.289 / Virus Database: 265.5.2 - Release Date: 12/13/2004


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.289 / Virus Database: 265.5.2 - Release Date: 12/13/2004
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to