Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #12390 > unrolled thread

Printing to a File using ReportPro 2.17 and VO 2.8 sp3

Started byJeff Rollo <jrollo64@gmail.com>
First post2019-04-06 01:32 -0700
Last post2019-04-09 06:17 +0200
Articles 13 — 5 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Printing to a File using ReportPro 2.17 and VO 2.8 sp3 Jeff Rollo <jrollo64@gmail.com> - 2019-04-06 01:32 -0700
    Re: Printing to a File using ReportPro 2.17 and VO 2.8 sp3 Johan Nel <johan.nel@xsinet.co.za> - 2019-04-06 11:11 +0200
      Re: Printing to a File using ReportPro 2.17 and VO 2.8 sp3 Carlos Rocha <j.carlos.rocha.1.SpyedBy@gmail.com> - 2019-04-06 13:34 +0100
        Re: Printing to a File using ReportPro 2.17 and VO 2.8 sp3 Jeff Rollo <jrollo64@gmail.com> - 2019-04-06 06:17 -0700
          Re: Printing to a File using ReportPro 2.17 and VO 2.8 sp3 "Jamal" <noooospam@example.com> - 2019-04-06 13:57 -0400
            Re: Printing to a File using ReportPro 2.17 and VO 2.8 sp3 Johan Nel <johan.nel@xsinet.co.za> - 2019-04-06 20:08 +0200
            Re: Printing to a File using ReportPro 2.17 and VO 2.8 sp3 Jeff Rollo <jrollo64@gmail.com> - 2019-04-06 17:41 -0700
        Re: Printing to a File using ReportPro 2.17 and VO 2.8 sp3 Johan Nel <johan.nel@xsinet.co.za> - 2019-04-06 15:19 +0200
          Re: Printing to a File using ReportPro 2.17 and VO 2.8 sp3 Carlos Rocha <j.carlos.rocha.1.SpyedBy@gmail.com> - 2019-04-06 15:45 +0100
            Re: Printing to a File using ReportPro 2.17 and VO 2.8 sp3 Johan Nel <johan.nel@xsinet.co.za> - 2019-04-06 19:36 +0200
          Re: Printing to a File using ReportPro 2.17 and VO 2.8 sp3 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2019-04-08 11:50 +0200
            Re: Printing to a File using ReportPro 2.17 and VO 2.8 sp3 Carlos Rocha <j.carlos.rocha.1.SpyedBy@gmail.com> - 2019-04-08 14:28 +0100
              Re: Printing to a File using ReportPro 2.17 and VO 2.8 sp3 "Wolfgang Riedmann" <wriedmann@gmail.com> - 2019-04-09 06:17 +0200

#12390 — Printing to a File using ReportPro 2.17 and VO 2.8 sp3

FromJeff Rollo <jrollo64@gmail.com>
Date2019-04-06 01:32 -0700
SubjectPrinting to a File using ReportPro 2.17 and VO 2.8 sp3
Message-ID<4e2f5e25-1558-42d0-b606-289d60c181ae@googlegroups.com>
Hi. As the subjects says, that's what I'm trying to acheive using THIS code...

Method PrintInvoice Class JobInfo
local oDB  as DBServer
Local CCode, cName, cPrint2Filename, cCaption, cMessage, cJobName, nJobNUmber //as string
Local oReport as RpReport  
nJobNUmber := self:oSFJobInfo_DETAIL:JOBNUMBER
cName := self:CLNAME
self:Hide()
		   oDB := self:oSFJobInfo_DETAIL:Server
		   oDB:Commit()
		      cJobName 		:= "Current Jobs Listing"
				cPrint2Filename	:= "Invoice Number " + self:oSFJobInfo_DETAIL:JOBNUMBER + " For " + Proper(cName) + ".pdf"  <== This is what I want the report (Invoice in this case) to be called. Not the PDF extension.
				cCaption		:= cAppVersion + " - Report Preview"
				cMessage		:= "Printing in progress..."
			oReport := RpReport{ self, "JobNumber.rpt"} 
			IF oReport:IsValid
	      oDB:SetOrder("JobNumber", "Details")
		   oDB:GoTop() 
		   oDB:Seek(nJobNUmber)
		   CCode := oDB:FIELDGET(#CLCode)
		   oDB:Close()
			
			oDB := CLIENT{self}
			oDB:Seek( AllTrim(CCode)) 

			cName := oDB:FIELDGET(#ClName)
		   oDB:Close()  
				   oReport:SetVariableValue("ClientHeading", "TAX Invoice " + nJobNUmber)   
               oReport:SetVariableValue("CCode", AllTrim(CCode))   
               oReport:SetVariableValue("CName", AllTrim(cName) ) 
               oReport:SetVariableValue("IsFin", .F.) 
				   oReport:PrintPreview(cJobName,cPrint2Filename,cCaption,cMessage,,SW_SHOWMAXIMIZED)
					self:Pointer := Pointer{ POINTERARROW }
		    ENDIF
        	oDB:Close()
			oReport:Close() 
		self:Show(SHOWCENTERED)
Return nil 


The <== are comments to help you understand what I'm doing

Any ideas please?

[toc] | [next] | [standalone]


#12391

FromJohan Nel <johan.nel@xsinet.co.za>
Date2019-04-06 11:11 +0200
Message-ID<q89qfe$83i$1@dont-email.me>
In reply to#12390
Jeff,

I have responded and will assist on the X# forums.  This NG is basically 
dead... People who will respond are all on the X# forums.

On 2019/04/06 10:32, Jeff Rollo wrote:
-- 
*Johan Nel*
FOX member: Friend(s) of XSharp
https://xsharp.info
George, South Africa

[toc] | [prev] | [next] | [standalone]


#12392

FromCarlos Rocha <j.carlos.rocha.1.SpyedBy@gmail.com>
Date2019-04-06 13:34 +0100
Message-ID<q8a6g9$j5d$1@dont-email.me>
In reply to#12391
You are pushing too much. This newsgroups is not dead yet, though you 
are doing your best to kill it for good.
This is about VO, a 32bit language, X# is about .NET

Às 10:11 de 06/04/2019, Johan Nel escreveu:
> Jeff,
> 
> I have responded and will assist on the X# forums.  This NG is basically 
> dead... People who will respond are all on the X# forums.
> 
> On 2019/04/06 10:32, Jeff Rollo wrote:


-- 
*Carlos Rocha*

---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus

[toc] | [prev] | [next] | [standalone]


#12393

FromJeff Rollo <jrollo64@gmail.com>
Date2019-04-06 06:17 -0700
Message-ID<079c7667-e349-4939-a36f-521ad00df634@googlegroups.com>
In reply to#12392
Well said Carlos, the XSharpers here seem to be far more intent on pushing the X# agenda, than answering VO questions...

[toc] | [prev] | [next] | [standalone]


#12399

From"Jamal" <noooospam@example.com>
Date2019-04-06 13:57 -0400
Message-ID<q8ap9j$vf3$1@news.albasani.net>
In reply to#12393
LOL, "X# Agenda" !!

BUT, the XSharpers answered your many questions here even though they have 
no obligation to do so!
You should be thankful they are still monitoring this dying NG and lending 
help when possible; not just asking questions and expecting answers!

Jamal

"Jeff Rollo"  wrote in message 
news:079c7667-e349-4939-a36f-521ad00df634@googlegroups.com...

Well said Carlos, the XSharpers here seem to be far more intent on pushing 
the X# agenda, than answering VO questions... 

[toc] | [prev] | [next] | [standalone]


#12400

FromJohan Nel <johan.nel@xsinet.co.za>
Date2019-04-06 20:08 +0200
Message-ID<q8apuj$l9t$1@dont-email.me>
In reply to#12399
Thank you Jamal,

Yes, it is not about promoting X#, it is to keep the VO/XBase flame 
burning.  The FoxPro forums are a lot more positive receiving the "X# 
Agenda", they realize they on a sinking ship and have to look at the 
future.  Rewriting millions of lines of code, is definitely not the way 
they see as "forward" thinking.

On 2019/04/06 19:57, Jamal wrote:
> LOL, "X# Agenda" !!
>
> BUT, the XSharpers answered your many questions here even though they 
> have no obligation to do so!
> You should be thankful they are still monitoring this dying NG and 
> lending help when possible; not just asking questions and expecting 
> answers!
-- 
*Johan Nel*
FOX member: Friend(s) of XSharp
https://xsharp.info
George, South Africa

[toc] | [prev] | [next] | [standalone]


#12401

FromJeff Rollo <jrollo64@gmail.com>
Date2019-04-06 17:41 -0700
Message-ID<8d65513a-e11f-4e8c-b5a4-dac8b639bdac@googlegroups.com>
In reply to#12399
Actually Jamal, this is a VO forum. People who answer the posts, I would take to be VO people. If they ALSO happen to be X# people, then that's great happy days. I posted this on X# forum also at Johans insistance. I thank him for his answers and help as I have ALWAYS made a point of doing with all people who have helped me. Oddly enough, the biggest help I received recently Jamal was from a member of this forum, who is NOT an X#er. That's not to say I'm ungrateful for all the help I have received from people in BOTH communities however, of course I am.

[toc] | [prev] | [next] | [standalone]


#12394

FromJohan Nel <johan.nel@xsinet.co.za>
Date2019-04-06 15:19 +0200
Message-ID<f6a8bf53-0022-9db7-7f15-1614cb5d1d8f@xsinet.co.za>
In reply to#12392
Carlos,

On 2019/04/06 14:34, Carlos Rocha wrote:
> You are pushing too much. This newsgroups is not dead yet, though you 
> are doing your best to kill it for good.
> This is about VO, a 32bit language, X# is about .NET
>
VO is for all purposes dead, just like Visual FoxPro.

Yes it is about VO, a 32bit language, X# is not just .NET.  X# is a 
64bit environment that provides VO compatibility, with minimal changes.  
X# already support VO, including VO Windows, Menus, every "unique" 
feature of VO inside of its language syntax options...

Why trying to market a product that is not even supported anymore, when 
there is X# that brings the newest technology (.NET) right onto your 
doorstep...  The choice is yours, are you opening the door when you hear 
the knock?

Needless to say, I am monitoring all the lively help Jeff was provided 
here, in the mean time on the X# VO forum, he has already received the 
solution to his problem within 2 hours.  5 hours here and still waiting 
for assistance...

Just my 2c worth of observation...

-- 
*Johan Nel*
FOX member: Friend(s) of XSharp
https://xsharp.info
George, South Africa

[toc] | [prev] | [next] | [standalone]


#12395

FromCarlos Rocha <j.carlos.rocha.1.SpyedBy@gmail.com>
Date2019-04-06 15:45 +0100
Message-ID<q8ae6f$bai$1@dont-email.me>
In reply to#12394
VO, as VB6, is "static", not dead. But it's still a stable WIN32 
environment that unfortunately was abandoned before it was finished. 
Even so I can do anything with by using VB6 for what is missing.

I don't want to argue against .NOT (although I could) because that's not 
the point, the point is VO IS a good win32 language and is more alive 
and useful than you think.

And if X# is related to VO then this newsgroup should cover it too, not 
the way around. Forcing Vulcan to be a closed group was one of the 
biggest Brian mistakes, imho.

Às 14:19 de 06/04/2019, Johan Nel escreveu:
> Carlos,
> 
> On 2019/04/06 14:34, Carlos Rocha wrote:
>> You are pushing too much. This newsgroups is not dead yet, though you 
>> are doing your best to kill it for good.
>> This is about VO, a 32bit language, X# is about .NET
>>
> VO is for all purposes dead, just like Visual FoxPro.
> 
> Yes it is about VO, a 32bit language, X# is not just .NET.  X# is a 
> 64bit environment that provides VO compatibility, with minimal changes. 
> X# already support VO, including VO Windows, Menus, every "unique" 
> feature of VO inside of its language syntax options...
> 
> Why trying to market a product that is not even supported anymore, when 
> there is X# that brings the newest technology (.NET) right onto your 
> doorstep...  The choice is yours, are you opening the door when you hear 
> the knock?
> 
> Needless to say, I am monitoring all the lively help Jeff was provided 
> here, in the mean time on the X# VO forum, he has already received the 
> solution to his problem within 2 hours.  5 hours here and still waiting 
> for assistance...
> 
> Just my 2c worth of observation...
> 


-- 
*Carlos Rocha*

---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus

[toc] | [prev] | [next] | [standalone]


#12398

FromJohan Nel <johan.nel@xsinet.co.za>
Date2019-04-06 19:36 +0200
Message-ID<q8ao22$8gc$1@dont-email.me>
In reply to#12395
Hi Carlos,

I do realise we can discuss till end of time, but that would be counter 
productive.  I understand your angle thought.

Robert did approach Brian before X# started, however they could not come 
to an agreement.  I think in that scenario, it is fair that X# don't 
piggy back on VO/Vulcan resources.

I agree, you can extend VO with VB6 etc.  It is however easy to extend 
X# with VB.NET, c#.  Bring to that by October as promised, the full 
functionality of Visual FoxPro will be available to all XBase language 
syntax supported.

How nice to be able to add to VO:

LOCAL cSql AS STRING
TEXT TO cSql
     SELECT * FROM <table>
         WHERE <fld> <= 'JJJ'
         ORDER BY <fld1>, <fld2>
END TEXT

There are other VFP commands also in the pipeline:
SCAN/END SCAN to name just one...

On 2019/04/06 16:45, Carlos Rocha wrote:
> VO, as VB6, is "static", not dead. But it's still a stable WIN32 
> environment that unfortunately was abandoned before it was finished. 
> Even so I can do anything with by using VB6 for what is missing.
>
> I don't want to argue against .NOT (although I could) because that's 
> not the point, the point is VO IS a good win32 language and is more 
> alive and useful than you think.
>
> And if X# is related to VO then this newsgroup should cover it too, 
> not the way around. Forcing Vulcan to be a closed group was one of the 
> biggest Brian mistakes, imho.
>
> Às 14:19 de 06/04/2019, Johan Nel escreveu:
>> Carlos,
>>
>> On 2019/04/06 14:34, Carlos Rocha wrote:
>>> You are pushing too much. This newsgroups is not dead yet, though 
>>> you are doing your best to kill it for good.
>>> This is about VO, a 32bit language, X# is about .NET
>>>
>> VO is for all purposes dead, just like Visual FoxPro.
>>
>> Yes it is about VO, a 32bit language, X# is not just .NET.  X# is a 
>> 64bit environment that provides VO compatibility, with minimal 
>> changes. X# already support VO, including VO Windows, Menus, every 
>> "unique" feature of VO inside of its language syntax options...
>>
>> Why trying to market a product that is not even supported anymore, 
>> when there is X# that brings the newest technology (.NET) right onto 
>> your doorstep...  The choice is yours, are you opening the door when 
>> you hear the knock?
>>
>> Needless to say, I am monitoring all the lively help Jeff was 
>> provided here, in the mean time on the X# VO forum, he has already 
>> received the solution to his problem within 2 hours.  5 hours here 
>> and still waiting for assistance...
>>
>> Just my 2c worth of observation...
>>
>
>
-- 
*Johan Nel*
FOX member: Friend(s) of XSharp
https://xsharp.info
George, South Africa

[toc] | [prev] | [next] | [standalone]


#12404

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2019-04-08 11:50 +0200
Message-ID<gh0jr8F1jadU1@mid.individual.net>
In reply to#12394
Hi Johan,

PMFJI,

> VO is for all purposes dead, just like Visual FoxPro.

VO is not dead, only it's development has been stopped, and that will
lead to the situation that it will be dead in a foreseable future.

It will be dead the day if VO applications will not run on the then
actual Windows version, or the VO IDE is not anymore able to build
applications (like it is the case with Clipper).

X# currently is the only option for VO programmers to make the
applications future proof (and you know how serious I take that!), but
the current X# release cannot be used to transport DBFCDX based VO
applications to NET, even if that will be the case in a few days.

But now VO programmers have to stick with VO, and prepare for the
migration, learning X# and .NET, until X# is really ready and some
people have migrated and tested their VO applications in X#

You know that I was one of the first ones to trust X# for production
applications (but either migrated from Vulcan or written from scratch),
and for sure I will start migrating my DBF bases VO applications to X#
when this is possible, and then I will try to help others to do the
same.

But not everyone is willing to move to X#, maybe because they not trust
the development team, maybe because nobody pays for a migration process
(that will be my case for some VO applications where customers are not
willing to pay for such a migration), or maybe because they feel not
ready for such a work.

Therefore there will be the need for support for VO programmers for
several years now, and not everyone is willing to change to the X#
forums, even if there are the real VO experts like the X# development
team.

So at least I for myself will continue to monitor this newsgroup at
least every few days.

And I don't think it is a good thing to create expectations that at the
moment cannot be fulfilled.

Wolfgang


-- 

[toc] | [prev] | [next] | [standalone]


#12409

FromCarlos Rocha <j.carlos.rocha.1.SpyedBy@gmail.com>
Date2019-04-08 14:28 +0100
Message-ID<q8ficc$it2$1@dont-email.me>
In reply to#12404
Wise words, Wolfgang.
I only disagree on the part that we MUST migrate to .NET.

In my view the current .net implementation will die in the day win32 
dies, as it deeply depends on win32 itself. Of course this can change 
when/if MS drops 32bit support within 64bit OS, as they did with 16bit 
apps in windows 64bit. And when/if that happens I'm sure we'll have some 
other train to catch (mobile, web, linux, cloud, whatever).

Às 10:50 de 08/04/2019, Wolfgang Riedmann escreveu:
> Hi Johan,
> 
> PMFJI,
> 
>> VO is for all purposes dead, just like Visual FoxPro.
> 
> VO is not dead, only it's development has been stopped, and that will
> lead to the situation that it will be dead in a foreseable future.
> 
> It will be dead the day if VO applications will not run on the then
> actual Windows version, or the VO IDE is not anymore able to build
> applications (like it is the case with Clipper).
> 
> X# currently is the only option for VO programmers to make the
> applications future proof (and you know how serious I take that!), but
> the current X# release cannot be used to transport DBFCDX based VO
> applications to NET, even if that will be the case in a few days.
> 
> But now VO programmers have to stick with VO, and prepare for the
> migration, learning X# and .NET, until X# is really ready and some
> people have migrated and tested their VO applications in X#
> 
> You know that I was one of the first ones to trust X# for production
> applications (but either migrated from Vulcan or written from scratch),
> and for sure I will start migrating my DBF bases VO applications to X#
> when this is possible, and then I will try to help others to do the
> same.
> 
> But not everyone is willing to move to X#, maybe because they not trust
> the development team, maybe because nobody pays for a migration process
> (that will be my case for some VO applications where customers are not
> willing to pay for such a migration), or maybe because they feel not
> ready for such a work.
> 
> Therefore there will be the need for support for VO programmers for
> several years now, and not everyone is willing to change to the X#
> forums, even if there are the real VO experts like the X# development
> team.
> 
> So at least I for myself will continue to monitor this newsgroup at
> least every few days.
> 
> And I don't think it is a good thing to create expectations that at the
> moment cannot be fulfilled.
> 
> Wolfgang
> 
> 


-- 
*Carlos Rocha*

---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus

[toc] | [prev] | [next] | [standalone]


#12411

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2019-04-09 06:17 +0200
Message-ID<gh2kmrFf90uU1@mid.individual.net>
In reply to#12409
Hi Carlos,

> I only disagree on the part that we MUST migrate to .NET.
> 
> In my view the current .net implementation will die in the day win32
> dies, as it deeply depends on win32 itself. Of course this can change
> when/if MS drops 32bit support within 64bit OS, as they did with
> 16bit apps in windows 64bit. And when/if that happens I'm sure we'll
> have some other train to catch (mobile, web, linux, cloud, whatever).

fortunately we can have different opinions.

But .NET (Core) is available on more platforms that Windows alone - but
you are right, the VO GUI classes will not run there.

IMHO the end of VO is approaching. It is a year or two that sometimes
the ressource compiler does not work any more and I have to restart VO
to make it work again - this is a problem more people are having.

And the entire platform is becoming old - many (new) things that I need
don't work, and for the moment I create .NET components in X# to tap
these shortcomings whenever possible.
Customers are more and more asking new GUIs that are available only in
.NET, and so I have to adapt.

Wolfgang


-- 

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web