I think you missed my point. this is a separate product you are creating

that will pull data from VFP and only store it online. You can then build

up a new style of reporting outside of VFP. Once they approve of it you

can delete the data older than 4 years or 7 years from the VFP

environment. The Data Scientist role may suit you very well.

Check out this:

https://www.zs.com/services/technology/technology-services/big-data-and-data-scientist-services.aspx

On Fri, Dec 29, 2017 at 10:34 AM, <

mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:

> Hi Steve,

>

> Again, it's not an issue with non-VFP backends like MySQL. This was about

> the VFP-backend folks. If I were to redesign an app, I would use MariaDB

> as the backend if I could.

>

> HNY!

> --Mike

>

>

>

> On 2017-12-29 11:26, Stephen Russell wrote:

>

>> Why not create a Data Warehouse for that data and archive it that way.

>> You

>> can put that into mySQL and remove it from .dbfs at the same time.

>>

>> Create your Fact and Dimension tables to contain the true data needed for

>> your DW over the long haul. Then you can investigate a variety of tools

>> to

>> enable Data Analytics going forward. This might give you some ideas on

>> that.

>> https://blog.capterra.com/free-and-open-source-data-visualization-tools/

>>

>>

>>

>> On Fri, Dec 29, 2017 at 9:47 AM, <

>> mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:

>>

>> I've seen long-time softwares with VFP backends that had a ton of data

>>> (10+ years worth) and I had devised a method in one case recently to be

>>> able to "archive" old data by storing it in a subfolder intelligently (so

>>> it could be easily retrieved and/or reimported into the main data set).

>>> I

>>> haven't used a VFP backend since 2004 when Bob Lee introduced me to the

>>> MySQL world but nonetheless I thought I'd ask if devs here ever put

>>> anything like an "archiving" feature into their software, and how they do

>>> it. In my case, instead of slinging 600MB of data across the network (in

>>> the case of one of my clients), my archiving showed a reduction of like

>>> 75%, so only 25% of that was being pulled across the LAN instead. (They

>>> didn't need all the data from the beginning of the App's time...they just

>>> needed relevant/recent data.)

>>>

>>> I realize that with MySQL and other such RDBMSes this is a non-issue, but

>>> I wanted to ask the VFP-backend folks their approach to this for the sake

>>> of (hopefully) interesting discussion. One final juicy thread before

>>> 2017

>>> is finished. :-)

>>>

[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/CAJidMYLA2BzfNwh5S6MfYj_-UM0uf-cjn5s0d41iBFPvNQ540w@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.