Andy -
Just create a handle for the Crystal object and load your report. You don't
need to use a vantage internal procedure - write your own for the last piece
of the puzzle.
HTH-
Calvin
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Andy Watts
Sent: Wednesday, May 21, 2008 4:14 AM
To: vantage@yahoogroups.com
Subject: [Vantage] 4GL Print a Crystal Report
To all the 4GL gurus out there,
Could anyone please offer me a pointer to how I can achieve the
following:
Aim:
From a 4GL procedure run from within a Vantage session, use the Vantage
internal procedure ...lib\crystal.r to print an AR Invoice using a
non-default crystal report, to a named printer. The underlying aim is to
be able to print an invoice through a PDFCreator printer driver,
resulting in a PDF file suitable for emailing. The crystal report is
non-default because it contains our corporate header - the standard one
doesn't since it prints on to pre-printed headed paper. We are one
Vantage 5.1, upgrading to 6.1 somewhen.
Achieved so far:
I call Vantage internal procedure ...ar\arf10-ur.r to create the
temporary .dbf files necessary to print a specifies AR Invoice (works
perfectly)
I can call Vantage internal procedure ...lib\crystalv.r to print a
preview using a specified crystal report file, and the previously
created .dbf files. This also works perfectly, but stops short of my
aim.
I want to be able to call Vantage internal procedure ...lib\crystal.r to
print to a named printer using a specified crystal report file, and the
previously created .dbf files. My stumbling block is last of the
required parameters, called DevMode in datatype MEMPTR. I believe that
this is a pointer to a memory location where some information relating
to the desired print device driver is held. This is where my head is
going under the water!
Specific question:
Is it possible and practical for me to determine what I should supply as
a value for MEMPTR-type parameter DevMode from my 4GL procedure? I can
supply code snippets if that would be useful to anyone considering a
response.
Now I realise that the information I'm after here is worth something, so
I would glady share the results of my efforts to some degree, if indeed
they come to anything useful. Thanks very much for entertaining my
convoluted question!
Andy.
Andy Watts
IT Manager
Ripley Engineering Ltd
Tel: 01256-473940/464167
Mob:
www.ripley-eng.co.uk
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
Just create a handle for the Crystal object and load your report. You don't
need to use a vantage internal procedure - write your own for the last piece
of the puzzle.
HTH-
Calvin
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Andy Watts
Sent: Wednesday, May 21, 2008 4:14 AM
To: vantage@yahoogroups.com
Subject: [Vantage] 4GL Print a Crystal Report
To all the 4GL gurus out there,
Could anyone please offer me a pointer to how I can achieve the
following:
Aim:
From a 4GL procedure run from within a Vantage session, use the Vantage
internal procedure ...lib\crystal.r to print an AR Invoice using a
non-default crystal report, to a named printer. The underlying aim is to
be able to print an invoice through a PDFCreator printer driver,
resulting in a PDF file suitable for emailing. The crystal report is
non-default because it contains our corporate header - the standard one
doesn't since it prints on to pre-printed headed paper. We are one
Vantage 5.1, upgrading to 6.1 somewhen.
Achieved so far:
I call Vantage internal procedure ...ar\arf10-ur.r to create the
temporary .dbf files necessary to print a specifies AR Invoice (works
perfectly)
I can call Vantage internal procedure ...lib\crystalv.r to print a
preview using a specified crystal report file, and the previously
created .dbf files. This also works perfectly, but stops short of my
aim.
I want to be able to call Vantage internal procedure ...lib\crystal.r to
print to a named printer using a specified crystal report file, and the
previously created .dbf files. My stumbling block is last of the
required parameters, called DevMode in datatype MEMPTR. I believe that
this is a pointer to a memory location where some information relating
to the desired print device driver is held. This is where my head is
going under the water!
Specific question:
Is it possible and practical for me to determine what I should supply as
a value for MEMPTR-type parameter DevMode from my 4GL procedure? I can
supply code snippets if that would be useful to anyone considering a
response.
Now I realise that the information I'm after here is worth something, so
I would glady share the results of my efforts to some degree, if indeed
they come to anything useful. Thanks very much for entertaining my
convoluted question!
Andy.
Andy Watts
IT Manager
Ripley Engineering Ltd
Tel: 01256-473940/464167
Mob:
www.ripley-eng.co.uk
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]