Wingz Hyperscript questi

Reply to david_barmann@wiltel.com DB> 1. When printing from a Wingz script, is there any way to specify DB> the printing paramters within the script without the user entering DB> the information? I need to print landscape, centered, from page DB> 1 to page 2, etc. Wingz defaults to bringing up the print setup The only way we were able to get around that *!^#%$ thing was to create a spread sheet, pull up the page set up for it and set everything exactly the way we wanted, and then save it. When our applications need to print we pull up a copy of that file. Now, here's the fun part. All of our information is displayed in dialog boxes. The data which is being displayed in those dialog boxes is stored in a temp sheet OFF SCREEN. We looked at creating a dialog box and then loading it directly from the database, but it was too slow using a loop. Wingzouput() works much faster and dumps it into a sheet, then we load the list boxes or whatever from the data in the sheet. So, we made the temp sheet off screen. Then when the user closes out the dialog box, we blow away the sheet too. Now, if the user hits the print button, we open up the preformatted sheet, which was saved off screen (different from the temp sheet), copy the data from the temp sheet to the preformatted sheet, define out print range, issue the print now command and close out the preformatted sheet. We originally thought to load the data into the preformatted sheet, but this was a problem for other reasons of our design. It doesn't have to be done that way. Getting the preformatted sheets off screen is fun under SCO unix. We have a write a script to move the sheet off screen and save it there. Oh, we have had lots of fun getting around problems in Wingz . . . I can't wait to move to HST (if it ever comes out for SCO Unix!). DB> 2. When using datalink within a script, if an SQL error is returned, DB> such as 'no rows found', a dialog box pops up, requiring the user DB> to click 'OK'. I can handle the error condition within the script DB> so the user does not need to see this message. Is there any way DB> to keep the dialog box from popping up? I can't remember if there was a db:xxxx you could set or not. I just know that we always send our query and then do a check before retrieving data. In the case of a while loop WHILE DB:DBGETROW() <> DB:A_READY. Or if we are going to use wingzoutput, IF DB:DESCRIBEROWSET() > 0 then load the data else display a message, hey nothing is there . . . Either way, we never give the Wingz dialog box a chance to come up. DB> 3. Is there any other place on the Net to find helpful Wingz DB> information? Not that I know of. I wish there was a group for Wingz/HST development. I feel like these tools get lost in the flood of other informix stuff here. I've been developing with Wingz for a couple of years now. I have run across most of the Wingz problems (ARGGHHH!!!!), but overall I still like it (provided everything has been fixed in HST). Anyways, if you have any questions, or need help, let me know. What type of work are you doing? I have some neat code for different things . . . Raymond Bowers Computer Sciences Corporation 703-914-8422 ___ X OLX 2.2 X I am a figment of a computer's imagination --------- Fidonet: Raymond Bowers 1:109/120 Internet: Raymond.Bowers@f120.n109.z1.fidonet.org