Simple quick reminder: save $50 by registering before the Early-bird
registration deadline this Sunday, July 31st.
If you still need to register, please head over to the registration Web site
today:
http://geekgatherings.com/Registration
Every registered attendee gets admission and white
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
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
VFP extensibility can bring many more enhancements than modifying the
core code.
Thierry Nivelet
Le 27/07/2016 à 11:32, Man-wai Chang a écrit :
COBOL is widely used in mainframe-based banking and insurance systems.
It would NOT die. Nobody has the nerve to touch those written
problems, as
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.
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 wrote:
> I just tested this under Windows 10, VFP9 SP2 and a
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
COBOL is widely used in mainframe-based banking and insurance systems.
It would NOT die. Nobody has the nerve to touch those written
problems, as there will be legal consequences if not death altering
them.
Should we pray for a miracle for VFP? What if someone resurrect VFP
and enhance it? :)
On
I'm in the middle of downsizing (painful!) so if there's anyone *in the
UK* who is supporting 'heritage' systems I have available a full
original set of manuals for VFP 3.0 pro and the main manuals for FPW 2.6
(also Netlib for Foxpro, but I can't see anyone wanting that!).
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
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.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
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-boun...@leafe.com] On Behalf Of Sytze de
Boer
Sent: 26 July 2016 22:12
12 matches
Mail list logo