I have found a couple of other odd things. One in the report there is a
var that is set to a note datatype which is concatenating 3 text
columns.
The other is that if the user sends this to her local HP 895Cse printer
she has to hit the page feed if she prints more than one page.
We have used the Novell Capture command had the user Capture a network
laser before starting RBase and this routine works... This is not what
is needed though because the user cannot go to this printer to get the
output.
My boss thought of a possiblity.. Could RBase be outrunning the 895Cse
printer .. ie: running past the memory in the printer?
Troy.. may have to go to a file first but this is not what we would like
to do.
Still fishin
Jim Limburg
Jim Limburg wrote:
>
> G-Day all
>
> Have any of you seen this one. We are using DOS6.0 until I can switch it
> to 6.5++ DOS..
> We have a report thats are based off a table that the user populates
> through an Enter form.
> This report has a few lookups and all seem to look ok in them. The user
> uses this at least 2-3 times a day and about once a week in the middle
> of the printing the report on each row which is usually about 10 to 50
> rows the user has entered it will stop printing. The rows in the table
> get deleted after this routine and the user has to re-enter..
>
> Where is the best place to look for problems.
>
> Here is the code that is being used to Enter to the table the report is
> based on and to print off of it.
>
> CASE 'Enter Forms to Print'
> CLS
> SET VAR whval0 TEXT
> DIALOG 'Enter E for Employee claim, D for Dependent:' whval0
> whtemp 1
> IF whval0 = 'E' THEN
> ENTER USING prtemp
> ENDIF
> IF whval0 = 'D' THEN
> ENTER USING prtdep
> ENDIF
> CLEAR VAR whval0
> RUN makeplay.cmd USING .pick11, 2
> BREAK
> CASE 'Print Forms'
> CLS
> DIALOG 'Ready to print?' vans whtemp YES
> IF vans = 'NO' THEN
> BREAK
> ENDIF
> SET PRINTER hpdesk2.prd
> OUTPUT LPT1:
> PRINT form2 WHERE ssnum IS NOT NULL
> IF errvar <> 0 THEN
> OUTPUT SCREEN
> PAUSE 1 USING 'No forms to print. Press any key to continue.'
> ENDIF
> OUTPUT SCREEN
> CLS
> SET VAR vans2 TEXT = NULL
> DIALOG 'Did forms print OK?' vans2 whtemp YES
> IF vans2 = 'YES' THEN
> DELETE FROM prtfrm
> ENDIF
> CLEAR VAR vans, vans2
> RUN makeplay.cmd USING .pick11, 3
> BREAK
>
> The other curious thing about this is that the report has several BOLD
> and BOLD OFF all the way through the report but it has one BOLD OFF for
> each BOLD so it doesn't look to be a problem..
>
> Huntin' and Peckin'
> Jim Limburg
