That's interesting.
I've been finding out that I can print my reports directly to a PDF using
CutePDF as my default printer which means rather than having to create an
excel spreadsheet or some other system like that, I can now create my
reports using vfp, add a button to print the report and send the pdf to them
which means they can search it, and print out just the pages that they need.

My first attempt was done yesterday analyzing all Texas Job Occupations and
it worked good.

http://keepamericaatwork.com/wp-content/uploads/2015/02/BIG_LIE_TX.pdf

I just need to make it more granular so that it won't be so big.

Basically I want to give them the ability to retrieve the data they are
interested in, and then give them the option to view a map to make it easier
to visualize the data, and/or print the data directly to a PDF

There probably is a way to do that with PHP, but I haven't run across it
yet.
I did see where I could connect to dbf's in php similar to what you're
describing here.

-----Original Message-----
From: ProFox [mailto:[email protected]] On Behalf Of Ken Dibble
Sent: Sunday, February 15, 2015 12:30 PM
To: [email protected]
Subject: Re: How to tell clients which "Windows" devices VFP runs on


>I think the real key is to define fox apps as requiring a host to run, 
>or as web based.
>
>In other words, if the data, etc is hosted on a box that will run vfp, 
>foxweb, westwind, etc. and they only want browser based apps, I believe 
>it will run on any tablet, phone, etc. if you're willing to design the
"app"
>for the screen size.

Well, as far as hosting data, you can put VFP dbfs and dbcs on any Linux box
running SAMBA and it works fine. So you don't need a "box that will run vfp"
to host data, even if you are using a VFP back end.

I have found that a Windows RDP server will handle my very complex VFP
applications very well. I have separate copies of the application set up on
the RDP server for each user's RDP account (primarily because my app is not
Windows-compliant on where it writes to locally), and they all access the
same VFP data on a CentOS box. The only bottlenecks are speed of the host
site's internet connection, speed of the user's internet connection, and,
potentially, printing. 
(Our RDP server is on a TW Telecom fiber optic line that has 25 Mbps
down/3 Mbps up and that seems quite adequate from our end.) RDP just sends
images across the wire for everything except printing. It can take up to a
minute for the local printer to respond to a print job requested over RDP,
but it still works fine.

Based on my reading of MS's white paper on the subject, I think you would
have no problem having 50 concurrent users running a complex VFP application
on a middling-power RDP server, and if you beef up the hardware you could
probably get closer to 150 per box.

There is a Mac RDP client, and since Mac is BSD Unix under the hood, I
wouldn't be surprised if there was a Linux RDP client available somewhere.
So it may be close to a universal solution for people using devices with
screens big enough to do data-entry.

Ken Dibble
www.stic-cil.org 


[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
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/[email protected]
** 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.

Reply via email to