[reordered to chronological]
At 02:26 2016-07-26, Dave Crozier DaveC@Flexipol.co.uk wrote:
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Sytze de Boer Sent: 26 July 2016 04:46 To: profox profox@leafe.com Subject: Windows 10 and Append General
So I have used this approach for 20 years and it has always worked My client prepares an invoice using Word The file is "INV"+alltrim(str(invnum))+".DOC" E.g. INV12345.DOC
Not a solution to your problem, but you might try transform(invnum) instead of the alltrim(str()).
No, No, No ... General fields are the work of the devil.... bloated memo files, VFP table size restrictions, links that get mysteriously corrupted, slow as hell etc.
One advantage of general fields is that the short form of the keyword is my first name.
Sincerely,
Gene Wirchenko
Thank you all for your opinions/advice.
I am happy to NOT store data in the General field, since the data is already saved in DOC format, which is unique to each invoice. ("INV"+alltrim(str(invnum))+".DOC"
My remaining issue though, is there some way I can print a report with the DOC file details.? (In much the same way as printing a report with a JPG file, or otherwise)
On Wed, Jul 27, 2016 at 5:29 AM, Gene Wirchenko genew@telus.net wrote:
[reordered to chronological]
At 02:26 2016-07-26, Dave Crozier DaveC@Flexipol.co.uk wrote:
-----Original Message-----
From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Sytze de Boer Sent: 26 July 2016 04:46 To: profox profox@leafe.com Subject: Windows 10 and Append General
So I have used this approach for 20 years and it has always worked My client prepares an invoice using Word The file is "INV"+alltrim(str(invnum))+".DOC" E.g. INV12345.DOC
Not a solution to your problem, but you might try transform(invnum)instead of the alltrim(str()).
No, No, No ... General fields are the work of the devil.... bloated memo
files, VFP table size restrictions, links that get mysteriously corrupted, slow as hell etc.
One advantage of general fields is that the short form of the keywordis my first name.
Sincerely,
Gene Wirchenko
[excessive quoting removed by server]
On Tue, Jul 26, 2016 at 3:56 PM, Sytze de Boer sytze.kiss@gmail.com wrote:
My remaining issue though, is there some way I can print a report with the DOC file details.? (In much the same way as printing a report with a JPG file, or otherwise)
I'm sorry for being dense, but what do you mean by that?
Are DOC file details the author's name and number of characters, e.g., the properties, or
Are you trying to print the DOC file, perhaps as an image embedded in a FoxPro FRX report?
Yes, I'm trying to print the Doc file embedded in a report. Like you can with a picture.
On Wed, Jul 27, 2016 at 9:08 AM, Ted Roche tedroche@gmail.com wrote:
On Tue, Jul 26, 2016 at 3:56 PM, Sytze de Boer sytze.kiss@gmail.com wrote:
My remaining issue though, is there some way I can print a report with
the
DOC file details.? (In much the same way as printing a report with a JPG file, or otherwise)
I'm sorry for being dense, but what do you mean by that?
Are DOC file details the author's name and number of characters, e.g., the properties, or
Are you trying to print the DOC file, perhaps as an image embedded in a FoxPro FRX report?
-- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com
[excessive quoting removed by server]
Yes, if you have the full path to the document file name you can use shellexecute to print it ... but you _might_ have to contend with a print dialog popping up
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Sytze de Boer Sent: 26 July 2016 22:12 To: profoxtech@leafe.com Subject: Re: Windows 10 and Append General
Yes, I'm trying to print the Doc file embedded in a report. Like you can with a picture.
On Wed, Jul 27, 2016 at 9:08 AM, Ted Roche tedroche@gmail.com wrote:
On Tue, Jul 26, 2016 at 3:56 PM, Sytze de Boer sytze.kiss@gmail.com wrote:
My remaining issue though, is there some way I can print a report with
the
DOC file details.? (In much the same way as printing a report with a JPG file, or otherwise)
I'm sorry for being dense, but what do you mean by that?
Are DOC file details the author's name and number of characters, e.g., the properties, or
Are you trying to print the DOC file, perhaps as an image embedded in a FoxPro FRX report?
-- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com
[excessive quoting removed by server]
That's how most do it!
Storing those files outside of VFP DBF files actually improve security and ease of management. You can make use of the file sytsem's features to manage them. In the case of extreme security breaches, you could just relocate if not delete the file, instead of having to dig into a GENERAL data type. Remember: it takes time to search then bang.mp3 a record in DBF!
On Wed, Jul 27, 2016 at 3:50 PM, Paul Newton Paul.Newton@pegasus.co.uk wrote:
Yes, if you have the full path to the document file name you can use shellexecute to print it ... but you _might_ have to contend with a print dialog popping up
On Tue, 26 Jul 2016, at 10:11 PM, Sytze de Boer wrote:
Yes, I'm trying to print the Doc file embedded in a report. Like you can with a picture.
I'm amazed that *ever* worked without getting involved in ReportListeners.
I just tested this under Windows 10, VFP9 SP2 and a small table with a general field linked to Word 2016 .docx files. It seems to indeed work fine once I set the properties of the report field to 'Scale Picture - Retain Shape'.
So again I would strongly suspect path resolution issues.
Okay, Sytze, Alan says it works fine.
Is it possible that you are trying to run 64-bit Office from within (always 32-bit) Visual FoxPro? That might cause a problem.
On Wed, Jul 27, 2016 at 4:59 AM, Alan Bourke alanpbourke@fastmail.fm wrote:
I just tested this under Windows 10, VFP9 SP2 and a small table with a general field linked to Word 2016 .docx files. It seems to indeed work fine once I set the properties of the report field to 'Scale Picture - Retain Shape'.
So again I would strongly suspect path resolution issues.
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
[excessive quoting removed by server]
In my case, I started with an invoice already in a PDF, as that's how I send them to clients. I'm a big fan of PDF for this purpose: they're not (easily) modified, the print pretty at the client's site regardless of their printers, and they make a professional appearance. Word, not so much.
Here's what I did to get an invoice to display on a report:
CREATE TABLE example FREE (examplepk i autoinc, invoice g) APPEND BLANK APPEND GENERAL invoice from sampleinvoice.pdf LINK CREATE REPORT example FROM example.dbf REPORT FORM example preview MODIFY REPORT example * Add in the general field and mess around with layout settings, settling on "Clip Contents" * The report shows up with a big blue 'e' -- a classic error message! This is the icon for Windows Edge, * in this case, the default PDF handler for Win10. * Visit the Adobe site, download the Adobe Reader DC and follow the prompts to make it the default handler. * REPEAT the Append General step (since the first general field is linked to Edge) and Preview the Report. * Voila! WYSIWYG Invoice on a report form in six lines of code.
On Wed, Jul 27, 2016 at 7:17 AM, Ted Roche tedroche@gmail.com wrote:
Okay, Sytze, Alan says it works fine.
Is it possible that you are trying to run 64-bit Office from within (always 32-bit) Visual FoxPro? That might cause a problem.
On Wed, Jul 27, 2016 at 4:59 AM, Alan Bourke alanpbourke@fastmail.fm wrote:
I just tested this under Windows 10, VFP9 SP2 and a small table with a general field linked to Word 2016 .docx files. It seems to indeed work fine once I set the properties of the report field to 'Scale Picture - Retain Shape'.
So again I would strongly suspect path resolution issues.
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
[excessive quoting removed by server]
On 2016-07-27 04:59, Alan Bourke wrote:
I just tested this under Windows 10, VFP9 SP2 and a small table with a general field linked to Word 2016 .docx files. It seems to indeed work fine once I set the properties of the report field to 'Scale Picture - Retain Shape'.
So again I would strongly suspect path resolution issues.
Ever since folks long ago suggested to NOT embed files into General fields (but rather store the LINK to the file instead), I avoided using General fields.
Update Thank you all for your comments/opinions or otherwise.
My client has reversed the Win10 update and all is well again. i.e. same pc, same office, no change to my application.
It simply fails to "append general", as in it skips this line in my code. So now I have time to apply a work-around.....
On Thu, Jul 28, 2016 at 9:05 AM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2016-07-27 04:59, Alan Bourke wrote:
I just tested this under Windows 10, VFP9 SP2 and a small table with a general field linked to Word 2016 .docx files. It seems to indeed work fine once I set the properties of the report field to 'Scale Picture - Retain Shape'.
So again I would strongly suspect path resolution issues.
Ever since folks long ago suggested to NOT embed files into General fields (but rather store the LINK to the file instead), I avoided using General fields.
[excessive quoting removed by server]
-
Alan Bourke -
Gene Wirchenko -
Man-wai Chang -
mbsoftwaresolutions＠mbsoftwaresolutions.com -
Paul Newton -
Sytze de Boer -
Ted Roche