I'm guessing the cursor isn't processing thousands of rows, is it?  Because of 
course remember my previous post about how my cursor would hit a "critical 
mass" and crash out when it hit > 25,000 loops

Karen

 

 

 

-----Original Message-----
From: Jim Belisle <[email protected]>
To: rbase-l <[email protected]>
Sent: Wed, May 17, 2017 9:59 am
Subject: RE: [RBASE-L] - Strange printing problem



Whileopt is OFF (unchecked) and doing a unload reload did not show any errors 
so I do not think the DB is corrupted.
I may change the filename to include the drive to see if that will make a 
difference. It has not in the past but I am not sure where else to look.
 

James Belisle
 
Making Information Systems People Friendly Since 1990


 

From: [email protected] [mailto:[email protected]]On Behalf Of 
Buddy Walker
Sent: Wednesday, May 17, 2017 9:13 AM
To: [email protected]
Subject: RE: [RBASE-L] - Strange printing problem

 
Jim
  Your code looks ok but I would suggest getting the invoice# at the same time 
you are getting the control#. This would save a hit on the table. See below in 
red
  Make sure your variables are defined before the while loop
Buddy
 
SET VAR vinv INTEGER
SET VAR vord INTEGER
 
DECLARE c1 CURSOR FOR SELECT control#,invoice# FROM tinvcust ORDER BY control#
OPEN c1
FETCH c1 INTO vord INDICATOR ivord,vinv INDICATOR ivinv
WHILE SQLCODE <> 100 THEN
--  SET VAR vinv = invoice# FROM tinvcust WHERE control# = .vord
  SET VAR vfilename = ('PDFinvcust\'+.vinv+'.PDF')
  PRINT kayparkinvtemp WHERE control# = .vord OPTION PRINTER
  PRINT kayparkinvtemp WHERE control# = .vord +
  OPTION PDF +
  |FILENAME &vFileName +
  |TITLE Kay Park Recreation +
  |SUBJECT Invoice +
  |AUTHORIZATION Accounts Receivable +
  |OPEN OFF
  CLS
  FETCH c1 INTO vord INDICATOR ivord,vinv INDICATOR ivinv
ENDWHILE
DROP CURSOR c1
 
 
 

From: [email protected] [mailto:[email protected]]On Behalf Of 
Jim Belisle
Sent: Wednesday, May 17, 2017 9:33 AM
To: [email protected]
Subject: [RBASE-L] - Strange printing problem

 
We have been using the same code within RBASE 9.5 to print our invoices to a 
printer and create a PDF for almost two years now.
Starting yesterday, while trying to print the invoices (both a report and a 
PDF), printing starts then after printing three invoices, the RBASE session 
completely shuts down.
No ERROR codes show. RBASE completely shuts down. 
 
Last night I did a reload. The user did a test run this morning having the same 
result.
I decided to run the code outside of the application in the TRACE mode and 
everything printed fine and the PDFs were created. RBASE did not shut down.
 
Does anyone have any “Blues Clues”?
Below is the code I use in a cursor.
 
SET ERROR MESSAGE 705 OFF
DROP CURSOR c1
SET ERROR MESSAGE 705 ON
DECLARE c1 CURSOR FOR SELECT control# FROM tinvcust ORDER BY control#
OPEN c1
FETCH c1 INTO vord INDICATOR ivord
WHILE SQLCODE <> 100 THEN
  SET VAR vinv = invoice# FROM tinvcust WHERE control# = .vord
  SET VAR vfilename = ('PDFinvcust\'+.vinv+'.PDF')
  PRINT kayparkinvtemp WHERE control# = .vord OPTION PRINTER
  PRINT kayparkinvtemp WHERE control# = .vord +
  OPTION PDF +
  |FILENAME &vFileName +
  |TITLE Kay Park Recreation +
  |SUBJECT Invoice +
  |AUTHORIZATION Accounts Receivable +
  |OPEN OFF
  CLS
  FETCH c1 INTO vord INDICATOR ivord
ENDWHILE
DROP CURSOR c1
 
 
 
James Belisle
 
Making Information Systems People Friendly Since 1990

 
-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
[email protected].
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.




-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to