+1 800 256 3608 (toll-free in North America) or +49 7531 90 60 10| service@combit.com

Table not printing


(Guest) #1

We have a list that we print that is a remittance advice. The table header contains the details of the payment and the table shows the allocations of the payment againsteach invoice.

We have a customer who adds a payment and does not allocate the payment. In this circumstance the headings (variables) are printed but the table is not so the information about the payment itself is not shown.

The print loop is basically:

// Print header for first page
nRet := LlPrint(hJob)

goto first record with passed DB No
loop while DB ref on file = passed DB No and not eof()
if record is not a payment record
gather field info of record
// print table line
do while LlPrintFields(hJob) == LL_WRN_REPEAT_DATA
LlPrint(hJob)
enddo
endif
skip to next record
end loop

// print footer of last page
do while LlPrintFieldsEnd(hJob) == LL_WRN_REPEAT_DATA
enddo

// end List & Label print job
LlPrintEnd(hJob, 0)

LlJobClose(hJob)

I’ve modified it a little to make it readable.

I’ve seen that there is an option (LL_OPTION_DELAYTABLEHEADER) that when set to TRUE will print the header when the 1st table line is printed or FALSE which sets it to print when the 1st LLPrint() is called (which it says is the default).

As I have not used this option setting anywhere, I presume that it should always be printing the table (and therefore the header) immedialtely on the LLPrint call…

Should this be the case? Is there something wrong with my code logic? Can what I want to be done actually be done?

Thanks
Regan


(Guest) #2

Set LL_OPTION_DELAYTABLEHEADER to FALSE.

If you use an OCX or some other control, check the value of the
appropriate property.

Paulchen

“Regan Cawkwell” <regan@rbau…> wrote in message
news:14787232008122510@combit.net

We have a list that we print that is a remittance advice. The table
header contains the details of the payment and the table shows the
allocations of the payment againsteach invoice.

We have a customer who adds a payment and does not allocate the
payment. In this circumstance the headings (variables) are printed
but the table is not so the information about the payment itself is
not shown.

The print loop is basically:

// Print header for first page
nRet := LlPrint(hJob)

goto first record with passed DB No
loop while DB ref on file = passed DB No and not eof()
if record is not a payment record
gather field info of record
// print table line
do while LlPrintFields(hJob) == LL_WRN_REPEAT_DATA
LlPrint(hJob)
enddo
endif
skip to next record
end loop

// print footer of last page
do while LlPrintFieldsEnd(hJob) == LL_WRN_REPEAT_DATA
enddo

// end List & Label print job
LlPrintEnd(hJob, 0)

LlJobClose(hJob)

I’ve modified it a little to make it readable.

I’ve seen that there is an option (LL_OPTION_DELAYTABLEHEADER) that
when set to TRUE will print the header when the 1st table line is
printed or FALSE which sets it to print when the 1st LLPrint() is
called (which it says is the default).

As I have not used this option setting anywhere, I presume that it
should always be printing the table (and therefore the header)
immedialtely on the LLPrint call…

Should this be the case? Is there something wrong with my code
logic? Can what I want to be done actually be done?

Thanks
Regan


(Guest) #3

Hi Paul

Set LL_OPTION_DELAYTABLEHEADER to FALSE.

If you use an OCX or some other control, check the value of the
appropriate property.

I ended up doing this, thanks.

What was annoying was that the documentation says that the default value for the above is FALSE.

I did use the GetOption API function to find out what it is set to and it returned TRUE. So this is clearly not the case.

Is this a documentation error?

Regan


(Guest) #4

I did never need that trick as far as I remember. But if you read TRUE
and the docs say FALSE, the docs are wrong, I would say. :wink:

Paulchen

“Regan Cawkwell” <regan@rbau…> wrote in message
news:367257242008174018@combit.net

Hi Paul

Set LL_OPTION_DELAYTABLEHEADER to FALSE.

If you use an OCX or some other control, check the value of the
appropriate property.

I ended up doing this, thanks.

What was annoying was that the documentation says that the default
value for the above is FALSE.

I did use the GetOption API function to find out what it is set to
and it returned TRUE. So this is clearly not the case.

Is this a documentation error?

Regan