Re: frx to html conversion

[Fernando D. Bozzo]

@Mike:

The FOXOBJECT only applies wheh iterating over an object matrix, like
objects or controls or any object collection, not for iterating properties
or character arrays

In any case I did learn that it's always better to iterate using for i = 1
to x syntax, because normally you need to know the position of the item on
the array to do something else, even just logging what you have done on
which element or the like


El 20/6/2017 9:07,  escribió:

> On 2017-06-19 12:15, Fernando D. Bozzo wrote:
>
>> Hi Paul:
>>
>> Just in case you didn't already think on possible setting's that can
>> affect
>> the performance heavily, and you keep looking what is different in VFP 9
>> that can make things so slow, I give you one that could be the
>> responsible:
>>
>> Using for..each for looping into a VFP object without using the new
>> keyword
>> FOXOBJECT
>> I think that it is the most important change that need a code change to
>> maintain compatibility.
>> If the for..each is for looping a com object, then no problem, but if the
>> object is a VFP object, then not having the FOXOBJECT keyword make VFP
>> treat the object as a com one, making it's access really slow
>>
>
>
>
> Just when I thought I couldn't learn anything more about VFP9you
> educated me on the FOXOBJECT keyword.  I often use FOR EACH loops, and
> they're ALWAYS fox objects.  I'll have to remember this tip.
>
> Thanks, Fernando!
> --Mike
>
>
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/CAGQ_JumEH37dvFzGsqpgAH=xbylkgkko2z0r4wzfmdtatvg...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[mbsoftwaresolutions]

On 2017-06-19 12:15, Fernando D. Bozzo wrote:

Hi Paul:

Just in case you didn't already think on possible setting's that can 
affect
the performance heavily, and you keep looking what is different in VFP 
9
that can make things so slow, I give you one that could be the 
responsible:


Using for..each for looping into a VFP object without using the new 
keyword

FOXOBJECT
I think that it is the most important change that need a code change to
maintain compatibility.
If the for..each is for looping a com object, then no problem, but if 
the

object is a VFP object, then not having the FOXOBJECT keyword make VFP
treat the object as a com one, making it's access really slow




Just when I thought I couldn't learn anything more about VFP9you 
educated me on the FOXOBJECT keyword.  I often use FOR EACH loops, and 
they're ALWAYS fox objects.  I'll have to remember this tip.


Thanks, Fernando!
--Mike


___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/f2ea5054289953aa03a736d2edc51...@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Paul Hemans]

@Ted that is an interesting approach. If I understand you correctly, run
the report take the output and use that as the basis of a template. Very
nice.

I am looking at +50 reports.

As far as a JS reporting engine goes we haven't really decided at this
point. We are toying with possibly using online spreadsheets as a more
flexible option. However, we still have the problem that we must produce
barcoded labels and the best platform for that seems to be PDF or XPS.
Looking at https://www.npmjs.com/package/html-pdf

On Tue, Jun 20, 2017 at 12:15 AM, Ted Roche  wrote:

> On Sun, Jun 18, 2017 at 7:03 PM, Paul Hemans 
> wrote:
> > Is anyone aware of a utility that will take a vfp8 report .frx / .frt and
> > convert it into some form of html template? To clarify, I am not looking
> to
> > run a vfp report and have it output in html.
>
> However, if you run all of your VFP reports and have it output to
> HTML, you will have the skeleton of an HTML template. You'll "just"
> need to replace the specific data with whatever placeholder/expression
> your new report engine uses.
>
> > We need to take a number of fairly simple reports and permanently move
> them
> > to html. I expect to have to do some editing to clean them up.
>
> When you say, "a number" do you mean a single digit or four digits, or
> something in between? The level of effort required might help
> understand how much work you're willing to do to avoid the gruntwork
> of manual conversion.
>
> > The application currently outputs pdfs from frx and they are presented on
> > the web. However, to better support i18n the database is moving to
> > Postgres, and the code to JS, that leaves a problem with the reports.
>
> Since you're going to PostgreSQL and JavaScript, which implies
> Unicode, I would avoid VFP and Window's clunky code page and
> double-byte character solutions, as they just make a mess.
>
> Has your dev team selected a JS reporting engine? This will really
> guide what you need to create. If you've decided to do it yourself,...
>
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/CAKT3oPcVO_K7i=cxgugj8gr4qc-wg13xsa9dhk_4htykgz8...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Paul Hemans]

@Koen would running the reports under vfp9 make it any more unicode
friendly?

On Mon, Jun 19, 2017 at 11:12 PM, Koen Piller  wrote:

> Paul
> I am not going to try to solve your VFP8 conversion to VFP9 problem,
> although I am convinced it can and should be solved.
> To stay on VFP8 and still make use of Foxypreviewr which only runs under
> VFP9SP2 I have once seen the following successfully:
> Built a project under VFP9SP2 with Foxypreviewer
> Create a report using your data and print it with FP
> Test
> Compile to an exe
> In your VFP 8 pjx call this exe when you want to print. It works No
> problem.
> Good luck
> Regards Koen
> PS FoxyPreviewer has an export facility to print to HTML
>
>
> Op ma 19 jun. 2017 om 14:55 schreef Paul Hemans  >
>
> > Koen, honestly why I am using vfp8 is a long (frustrating) story. The
> short
> > story is that I wrote a huge development environment with its own
> compiler,
> > I won't bore you with the details :) suffice to say that I am not kidding
> > when I say it is huge.
> > It runs fine under vfp8, but under vfp9 something changed internally with
> > the string handling. One of the features of the environment is that the
> > compiler turns html with embedded vfp into classes. Under vfp9 this
> process
> > runs incredibly slow. Under vfp8 an installation (which is when the
> > compiling happens) takes about 20 minutes, under vfp9 it took 6 hours.
> > I have spent a lot of time trying to sort it out. I have played with the
> > memory settings and with the coverage trying to track it down and in the
> > end, I hate to say it but it beat me.
> >
> >
> >
> > On Mon, Jun 19, 2017 at 10:36 PM, Koen Piller 
> > wrote:
> >
> > > Paul,
> > > upgrade to VFP9SP2 and make use of FoxyPreviewer.
> > > FoxyPreviewer has different export/saving options, amongst HTML
> > > Easy to use.
> > > Why do you stick to VFP8 anyway?
> > > Regards,
> > > Koen
> > >
> > > 2017-06-19 1:03 GMT+02:00 Paul Hemans :
> > >
> > > > Is anyone aware of a utility that will take a vfp8 report .frx / .frt
> > and
> > > > convert it into some form of html template? To clarify, I am not
> > looking
> > > to
> > > > run a vfp report and have it output in html.
> > > >
> > > > We need to take a number of fairly simple reports and permanently
> move
> > > them
> > > > to html. I expect to have to do some editing to clean them up.
> > > >
> > > > The application currently outputs pdfs from frx and they are
> presented
> > on
> > > > the web. However, to better support i18n the database is moving to
> > > > Postgres, and the code to JS, that leaves a problem with the reports.
> > > >
> > > > Thanks.
> > > >
> > > >
> > > > --- StripMime Report -- processed MIME parts ---
> > > > multipart/alternative
> > > >   text/plain (text body -- kept)
> > > >   text/html
> > > > ---
> > > >
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/cakt3opfhmvyqpwayqtseu0jboi3bnzkibxxgn-9d5xf0oct...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Paul Hemans]

@Fernando that is a great point and one that I had completely missed.
Really appreciate the input.

On Tue, Jun 20, 2017 at 2:15 AM, Fernando D. Bozzo 
wrote:

> Hi Paul:
>
> Just in case you didn't already think on possible setting's that can affect
> the performance heavily, and you keep looking what is different in VFP 9
> that can make things so slow, I give you one that could be the responsible:
>
> Using for..each for looping into a VFP object without using the new keyword
> FOXOBJECT
> I think that it is the most important change that need a code change to
> maintain compatibility.
> If the for..each is for looping a com object, then no problem, but if the
> object is a VFP object, then not having the FOXOBJECT keyword make VFP
> treat the object as a com one, making it's access really slow
>
>
>
> El 19/6/2017 2:55 p. m., "Paul Hemans" 
> escribió:
>
> > Koen, honestly why I am using vfp8 is a long (frustrating) story. The
> short
> > story is that I wrote a huge development environment with its own
> compiler,
> > I won't bore you with the details :) suffice to say that I am not kidding
> > when I say it is huge.
> > It runs fine under vfp8, but under vfp9 something changed internally with
> > the string handling. One of the features of the environment is that the
> > compiler turns html with embedded vfp into classes. Under vfp9 this
> process
> > runs incredibly slow. Under vfp8 an installation (which is when the
> > compiling happens) takes about 20 minutes, under vfp9 it took 6 hours.
> > I have spent a lot of time trying to sort it out. I have played with the
> > memory settings and with the coverage trying to track it down and in the
> > end, I hate to say it but it beat me.
> >
> >
> >
> > On Mon, Jun 19, 2017 at 10:36 PM, Koen Piller 
> > wrote:
> >
> > > Paul,
> > > upgrade to VFP9SP2 and make use of FoxyPreviewer.
> > > FoxyPreviewer has different export/saving options, amongst HTML
> > > Easy to use.
> > > Why do you stick to VFP8 anyway?
> > > Regards,
> > > Koen
> > >
> > > 2017-06-19 1:03 GMT+02:00 Paul Hemans :
> > >
> > > > Is anyone aware of a utility that will take a vfp8 report .frx / .frt
> > and
> > > > convert it into some form of html template? To clarify, I am not
> > looking
> > > to
> > > > run a vfp report and have it output in html.
> > > >
> > > > We need to take a number of fairly simple reports and permanently
> move
> > > them
> > > > to html. I expect to have to do some editing to clean them up.
> > > >
> > > > The application currently outputs pdfs from frx and they are
> presented
> > on
> > > > the web. However, to better support i18n the database is moving to
> > > > Postgres, and the code to JS, that leaves a problem with the reports.
> > > >
> > > > Thanks.
> > > >
> > > >
> > > > --- StripMime Report -- processed MIME parts ---
> > > > multipart/alternative
> > > >   text/plain (text body -- kept)
> > > >   text/html
> > > > ---
> > > >
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/CAKT3oPdXDXRuGWtmh2Q4OB=zdOL85EsVzy=SKsNQyaQ3W=o...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Fernando D. Bozzo]

Hi Paul:

Just in case you didn't already think on possible setting's that can affect
the performance heavily, and you keep looking what is different in VFP 9
that can make things so slow, I give you one that could be the responsible:

Using for..each for looping into a VFP object without using the new keyword
FOXOBJECT
I think that it is the most important change that need a code change to
maintain compatibility.
If the for..each is for looping a com object, then no problem, but if the
object is a VFP object, then not having the FOXOBJECT keyword make VFP
treat the object as a com one, making it's access really slow



El 19/6/2017 2:55 p. m., "Paul Hemans"  escribió:

> Koen, honestly why I am using vfp8 is a long (frustrating) story. The short
> story is that I wrote a huge development environment with its own compiler,
> I won't bore you with the details :) suffice to say that I am not kidding
> when I say it is huge.
> It runs fine under vfp8, but under vfp9 something changed internally with
> the string handling. One of the features of the environment is that the
> compiler turns html with embedded vfp into classes. Under vfp9 this process
> runs incredibly slow. Under vfp8 an installation (which is when the
> compiling happens) takes about 20 minutes, under vfp9 it took 6 hours.
> I have spent a lot of time trying to sort it out. I have played with the
> memory settings and with the coverage trying to track it down and in the
> end, I hate to say it but it beat me.
>
>
>
> On Mon, Jun 19, 2017 at 10:36 PM, Koen Piller 
> wrote:
>
> > Paul,
> > upgrade to VFP9SP2 and make use of FoxyPreviewer.
> > FoxyPreviewer has different export/saving options, amongst HTML
> > Easy to use.
> > Why do you stick to VFP8 anyway?
> > Regards,
> > Koen
> >
> > 2017-06-19 1:03 GMT+02:00 Paul Hemans :
> >
> > > Is anyone aware of a utility that will take a vfp8 report .frx / .frt
> and
> > > convert it into some form of html template? To clarify, I am not
> looking
> > to
> > > run a vfp report and have it output in html.
> > >
> > > We need to take a number of fairly simple reports and permanently move
> > them
> > > to html. I expect to have to do some editing to clean them up.
> > >
> > > The application currently outputs pdfs from frx and they are presented
> on
> > > the web. However, to better support i18n the database is moving to
> > > Postgres, and the code to JS, that leaves a problem with the reports.
> > >
> > > Thanks.
> > >
> > >
> > > --- StripMime Report -- processed MIME parts ---
> > > multipart/alternative
> > >   text/plain (text body -- kept)
> > >   text/html
> > > ---
> > >
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/CAGQ_Ju=u2ZxrR0A1Qs2xWTgOgyXYem8Cp9PnbeFb=nxzc6w...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

RE: frx to html conversion

[Ivan Martinez (imvh.g.c)]

There´s a class https://msdn.microsoft.com/en-us/library/aa976670(v=vs.71).aspx

FRX to HTML Foundation Class

Visual Studio .NET 2003
CategoryInternet
Default Catalog Visual FoxPro Catalog\Foundation Classes\Internet
Class   _frx2html
Base Class  Custom
Class Library   _internet.vcx
Parent Class_custom
Sample  ...\Samples\Solution\Ffc\dohtml.scx
Remarks
This class converts a Visual FoxPro report (.FRX) to HTML. The class includes 
properties to control the scope, visual layout and HTML generation. For more 
information, see Genhtml.prg.
To use, drop the class on a project or form or, from the Component Gallery Item 
Shortcut Menu, select Add to Project or Add to Form. When you add the class to 
a form, Visual FoxPro opens a builder so you can specify the cSource, cOutFile, 
nGenOutput, and lAutonameOutput values. When you drop the class on a project, 
you can choose between adding the class or creating a subclass.
See Guidelines for Using Visual FoxPro Foundation Classes for more information 
on using foundation classes.
Properties, Events, Methods Description
cOutFile property   Specifies the name of the HTML file to create.
Default: ""
cSource propertySpecifies the source file from which to generate HTML.
Default: ""
nGenOutput property _GENHTML output options.
Default: 20 = Generate output file.
1 = Generate and display the output file in the Visual FoxPro editor.
2 = Generate and display the output file in Internet Explorer.
3 = Generate and display the output file after displaying a Save As dialog box
4 = Create a PUBLIC _oHTML object and generate a file.
5 = Create a PUBLIC _oHTML object without generating a file.
lAutoNameOutput propertySpecifies whether _GENHTML should automatically 
name the output file based on the source.
Default: .T.
cScope property Specifies the scope (for example, NEXT or ALL) for the output.
Default: ""
cStyle property Specifies the visual style as listed in the ID field of 
Genhtml.dbf.
Default: ""
GenHTML method  Generates HTML code by calling the Genhtml.prg program using 
properties specified in cSource, cOutput, and nGenOutFile.
Syntax: GenHTML( )
Return: none
Arguments: none


Ivan Martinez vo Halle

-Mensaje original-
De: ProfoxTech [mailto:profoxtech-boun...@leafe.com] En nombre de Paul Hemans
Enviado el: lunes, 19 de junio de 2017 9:29
Para: profoxt...@leafe.com
Asunto: Re: frx to html conversion

Alan, you are right. In (my view of) a perfect world I would be translating 
from frx to html views that could be interpreted by ejs.co I do still see the 
need for the PDFs as that is how we produce labels. The frx formatting is also 
nice eye candy, but the ability of HTML interfaces to drill through data is 
making it a pretty compelling platform.

On Mon, Jun 19, 2017 at 11:21 PM, Alan Bourke <alanpbou...@fastmail.fm>
wrote:

> My understanding is Paul wanted to convert FRX\FRT layouts to some 
> sort of HTML-based equivalent, rather than producing a HTML report.
>
> --
>   Alan Bourke
>   alanpbourke (at) fastmail (dot) fm
>
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/008401d2e90a$17e4efb0$47aecf10$@gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Ted Roche]

On Sun, Jun 18, 2017 at 7:03 PM, Paul Hemans  wrote:
> Is anyone aware of a utility that will take a vfp8 report .frx / .frt and
> convert it into some form of html template? To clarify, I am not looking to
> run a vfp report and have it output in html.

However, if you run all of your VFP reports and have it output to
HTML, you will have the skeleton of an HTML template. You'll "just"
need to replace the specific data with whatever placeholder/expression
your new report engine uses.

> We need to take a number of fairly simple reports and permanently move them
> to html. I expect to have to do some editing to clean them up.

When you say, "a number" do you mean a single digit or four digits, or
something in between? The level of effort required might help
understand how much work you're willing to do to avoid the gruntwork
of manual conversion.

> The application currently outputs pdfs from frx and they are presented on
> the web. However, to better support i18n the database is moving to
> Postgres, and the code to JS, that leaves a problem with the reports.

Since you're going to PostgreSQL and JavaScript, which implies
Unicode, I would avoid VFP and Window's clunky code page and
double-byte character solutions, as they just make a mess.

Has your dev team selected a JS reporting engine? This will really
guide what you need to create. If you've decided to do it yourself,...

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/CACW6n4vNgPfUV9x+oxmsZgaoxk=c4_n7g+0-vszpkefaz--...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Paul Hemans]

Alan, you are right. In (my view of) a perfect world I would be translating
from frx to html views that could be interpreted by ejs.co
I do still see the need for the PDFs as that is how we produce labels. The
frx formatting is also nice eye candy, but the ability of HTML interfaces
to drill through data is making it a pretty compelling platform.

On Mon, Jun 19, 2017 at 11:21 PM, Alan Bourke 
wrote:

> My understanding is Paul wanted to convert FRX\FRT layouts to some sort
> of HTML-based equivalent, rather than producing a HTML report.
>
> --
>   Alan Bourke
>   alanpbourke (at) fastmail (dot) fm
>
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/cakt3opehvdrldwrek09o3zduxjvtxm_2yfw5szqyntin5md...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Alan Bourke]

My understanding is Paul wanted to convert FRX\FRT layouts to some sort
of HTML-based equivalent, rather than producing a HTML report.

-- 
  Alan Bourke
  alanpbourke (at) fastmail (dot) fm

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/1497878509.2912608.1014071520.568cb...@webmail.messagingengine.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Koen Piller]

Paul
I am not going to try to solve your VFP8 conversion to VFP9 problem,
although I am convinced it can and should be solved.
To stay on VFP8 and still make use of Foxypreviewr which only runs under
VFP9SP2 I have once seen the following successfully:
Built a project under VFP9SP2 with Foxypreviewer
Create a report using your data and print it with FP
Test
Compile to an exe
In your VFP 8 pjx call this exe when you want to print. It works No problem.
Good luck
Regards Koen
PS FoxyPreviewer has an export facility to print to HTML


Op ma 19 jun. 2017 om 14:55 schreef Paul Hemans 

> Koen, honestly why I am using vfp8 is a long (frustrating) story. The short
> story is that I wrote a huge development environment with its own compiler,
> I won't bore you with the details :) suffice to say that I am not kidding
> when I say it is huge.
> It runs fine under vfp8, but under vfp9 something changed internally with
> the string handling. One of the features of the environment is that the
> compiler turns html with embedded vfp into classes. Under vfp9 this process
> runs incredibly slow. Under vfp8 an installation (which is when the
> compiling happens) takes about 20 minutes, under vfp9 it took 6 hours.
> I have spent a lot of time trying to sort it out. I have played with the
> memory settings and with the coverage trying to track it down and in the
> end, I hate to say it but it beat me.
>
>
>
> On Mon, Jun 19, 2017 at 10:36 PM, Koen Piller 
> wrote:
>
> > Paul,
> > upgrade to VFP9SP2 and make use of FoxyPreviewer.
> > FoxyPreviewer has different export/saving options, amongst HTML
> > Easy to use.
> > Why do you stick to VFP8 anyway?
> > Regards,
> > Koen
> >
> > 2017-06-19 1:03 GMT+02:00 Paul Hemans :
> >
> > > Is anyone aware of a utility that will take a vfp8 report .frx / .frt
> and
> > > convert it into some form of html template? To clarify, I am not
> looking
> > to
> > > run a vfp report and have it output in html.
> > >
> > > We need to take a number of fairly simple reports and permanently move
> > them
> > > to html. I expect to have to do some editing to clean them up.
> > >
> > > The application currently outputs pdfs from frx and they are presented
> on
> > > the web. However, to better support i18n the database is moving to
> > > Postgres, and the code to JS, that leaves a problem with the reports.
> > >
> > > Thanks.
> > >
> > >
> > > --- StripMime Report -- processed MIME parts ---
> > > multipart/alternative
> > >   text/plain (text body -- kept)
> > >   text/html
> > > ---
> > >
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/cacuu1suadcmjyajj03p0o_mmd25cn53u46ojk3re5xlw8rz...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Paul Hemans]

Koen, honestly why I am using vfp8 is a long (frustrating) story. The short
story is that I wrote a huge development environment with its own compiler,
I won't bore you with the details :) suffice to say that I am not kidding
when I say it is huge.
It runs fine under vfp8, but under vfp9 something changed internally with
the string handling. One of the features of the environment is that the
compiler turns html with embedded vfp into classes. Under vfp9 this process
runs incredibly slow. Under vfp8 an installation (which is when the
compiling happens) takes about 20 minutes, under vfp9 it took 6 hours.
I have spent a lot of time trying to sort it out. I have played with the
memory settings and with the coverage trying to track it down and in the
end, I hate to say it but it beat me.



On Mon, Jun 19, 2017 at 10:36 PM, Koen Piller  wrote:

> Paul,
> upgrade to VFP9SP2 and make use of FoxyPreviewer.
> FoxyPreviewer has different export/saving options, amongst HTML
> Easy to use.
> Why do you stick to VFP8 anyway?
> Regards,
> Koen
>
> 2017-06-19 1:03 GMT+02:00 Paul Hemans :
>
> > Is anyone aware of a utility that will take a vfp8 report .frx / .frt and
> > convert it into some form of html template? To clarify, I am not looking
> to
> > run a vfp report and have it output in html.
> >
> > We need to take a number of fairly simple reports and permanently move
> them
> > to html. I expect to have to do some editing to clean them up.
> >
> > The application currently outputs pdfs from frx and they are presented on
> > the web. However, to better support i18n the database is moving to
> > Postgres, and the code to JS, that leaves a problem with the reports.
> >
> > Thanks.
> >
> >
> > --- StripMime Report -- processed MIME parts ---
> > multipart/alternative
> >   text/plain (text body -- kept)
> >   text/html
> > ---
> >
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/cakt3opdc3gjrf9rqacqglxmmebalehcoyjjzar7wkv7mx2a...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Koen Piller]

Paul,
upgrade to VFP9SP2 and make use of FoxyPreviewer.
FoxyPreviewer has different export/saving options, amongst HTML
Easy to use.
Why do you stick to VFP8 anyway?
Regards,
Koen

2017-06-19 1:03 GMT+02:00 Paul Hemans :

> Is anyone aware of a utility that will take a vfp8 report .frx / .frt and
> convert it into some form of html template? To clarify, I am not looking to
> run a vfp report and have it output in html.
>
> We need to take a number of fairly simple reports and permanently move them
> to html. I expect to have to do some editing to clean them up.
>
> The application currently outputs pdfs from frx and they are presented on
> the web. However, to better support i18n the database is moving to
> Postgres, and the code to JS, that leaves a problem with the reports.
>
> Thanks.
>
>
> --- StripMime Report -- processed MIME parts ---
> multipart/alternative
>   text/plain (text body -- kept)
>   text/html
> ---
>
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/CACUu1SvjcqUSrbwdWKhmBmLx06=vx4a5y8sqsj6ayqonjpq...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Paul Hemans]

Thierry I agree about PDFs, however frxs just don't fit with the direction
we are heading with system development. It's a pity because I liked the vfp
reporting and we have a tonne of reports coded.
Maybe I'll have to try a vfp report runner COM server that can switch code
pages.

On Mon, Jun 19, 2017 at 7:47 PM, Thierry Nivelet 
wrote:

> For reports, PDF is more consistent than HTML: fixed vs 'floating'
> positioning.
>
> Using JS, you can display a PDF report in a child window, or a new browser
> tab or window
>
> Thierry Nivelet
> http://foxincloud.com/
> Give your VFP app a second life in the cloud
>
> > Le 19 juin 2017 à 11:19, Alan Bourke  a écrit :
> >
> > I don't think such a thing exists - I would guess most people find it
> > quicker to just re-do them.
> >
> > --
> >  Alan Bourke
> >  alanpbourke (at) fastmail (dot) fm
> >
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/CAKT3oPeNYJprjnkyZECgHXx=_Js-jhZYrUr=alvzadzaiyh...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Thierry Nivelet]

For reports, PDF is more consistent than HTML: fixed vs 'floating' positioning.

Using JS, you can display a PDF report in a child window, or a new browser tab 
or window

Thierry Nivelet
http://foxincloud.com/
Give your VFP app a second life in the cloud

> Le 19 juin 2017 à 11:19, Alan Bourke  a écrit :
> 
> I don't think such a thing exists - I would guess most people find it
> quicker to just re-do them.
> 
> -- 
>  Alan Bourke
>  alanpbourke (at) fastmail (dot) fm
> 
[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/419c5c2d-2890-4f74-8478-e6c9f45f4...@foxincloud.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Alan Bourke]

I don't think such a thing exists - I would guess most people find it
quicker to just re-do them.

-- 
  Alan Bourke
  alanpbourke (at) fastmail (dot) fm

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/1497863961.1474259.1013839376.13448...@webmail.messagingengine.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Re: frx to html conversion

[Kurt at VR-FX]

I wonder in Fox-in-Cloud does something like that!


What do you say Thierry???

-K-

On 6/18/2017 7:03 PM, Paul Hemans wrote:

Is anyone aware of a utility that will take a vfp8 report .frx / .frt and
convert it into some form of html template? To clarify, I am not looking to
run a vfp report and have it output in html.

We need to take a number of fairly simple reports and permanently move them
to html. I expect to have to do some editing to clean them up.

The application currently outputs pdfs from frx and they are presented on
the web. However, to better support i18n the database is moving to
Postgres, and the code to JS, that leaves a problem with the reports.

Thanks.


--- StripMime Report -- processed MIME parts ---
multipart/alternative
   text/plain (text body -- kept)
   text/html
---


[excessive quoting removed by server]

___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/f03bd350-ea86-eb5d-55b8-e354d72db...@optonline.net
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.