Javier, Thanks for the tip. Took a stab at this today. Did the following: 1) Ran the report from the R prompt as you suggested and it came up properly. 2) Ran the form in the explorer mode through the form, hit the report button and it came up properly. For both of the above I used my working DB. 3) Changed the code within the form to capture error variables then compiled with updated form included. 4) After compiling, I hit the button on the form to run the report. A blank page came to the screen. The PAUSE statement showed no errors. No report information, just a blank page.
James Belisle Making Information Systems People Friendly Since 1990 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Javier Valencia Sent: Tuesday, April 08, 2014 4:23 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: STRANGE REPORT PROBLEM Jim, Is assembly# text or numeric? What happens if you comment out the code you have and simply place a command such as: -- If assembly# numeric: PRINT assemblycost WHERE Assembly# = 123 + OPTION SCREEN|Window_State MAXIMIZED -- If assembly# Text: PRINT assemblycost WHERE Assembly# = 'ABC' + OPTION SCREEN|Window_State MAXIMIZED This way you take the variable out. You can run it from the R> prompt first to make sure you have the right values for assembly# and the report runs correctly. Also, can you turn Messages and Error Messages on to make sure you are not getting an error message? Have you tried using the error variable to capture potential error messages? At the beginning of your print utility add: SET ERROR VARIABLE vErrorVariable --your print code goes here ... --Use both cases below to make sure the code is not being by-passed IF vErrorVariable <> 0 THEN PAUSE 2 USING . vErrorVariable CAPTION 'Error Message Present...' ICON APP ELSE PAUSE 2 USING 'No error present' CAPTION 'Error Message Not Present...' ICON APP ENDIF ... The rest of your print code. Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle Sent: Tuesday, April 08, 2014 1:32 PM To: RBASE-L Mailing List Subject: [RBASE-L] - STRANGE REPORT PROBLEM Frank, I completely recreated the report but got the same result after compiling it. The code is so simple and the same as I have for other reports on the same form. Assemblycost is the report name. The report works when in the explorer mode when using the WHERE builder. In the application it does not work. Below is the simple code I use. The same code is used on another report that works. SELECT (COUNT(*)) INTO vac2 INDICATOR ivac2 FROM assy_part + WHERE assembly# = .vpartnumid IF vac2 = 0 THEN PAUSE 1 USING 'Information not available. Use Assy_Part Entry Button!' + CAPTION 'Assembly Part Information' BUTTON 'Finish' GOTO done ELSE PRINT assemblycost WHERE assembly# = .vpartnumid + OPTION SCREEN|WINDOW_STATE MAXIMIZED + |ZOOM_TYPE PERCENTAGE|ZOOMPERCENT 100 ENDIF RECALC VAR LABEL done CLEAR VAR vac2, ivac2 SKIP TO partnum RETURN James Belisle Making Information Systems People Friendly Since 1990 --- RBASE-L =======================3D=======================3 D= TO POST A MESSAGE TO ALL MEMBERS: Send a plain text email to [email protected] (Don't use any of these words as your Subject: INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH, REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP) =======================3D=======================3 D= TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: INTRO =======================3D=======================3 D= TO UNSUBSCRIBE: Send a plain text email to [email protected] In the message SUBJECT, put just one word: UNSUBSCRIBE =======================3D=======================3 D= TO SEARCH ARCHIVES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: SEARCH-n (where n is the number of days). In the message body, place any text to search for. =======================3D=======================3 D=
