FP was not at SCOForum... why not

[John Esak]

> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com
> [mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of
> Christopher Yerry
> Sent: Saturday, August 13, 2005 12:27 PM
> To: Filepro-list at lists.celestial.com
> Subject: RE: FP was not at SCOForum... why not
>
>
> To add my "unasked for" 2 cents.
> Do not put all of your talents into any one product - Especially
> not one that does not do the big
> shows that they had always done in the past.
>
> I re read Eduardo Fernandez' (8/4/05) comments on his sons
> writing engines for filepro to be used
> externally - What is with the "old person" mentality I have been
> writing filePro for 18+ years But
> I also know how to write in 10 other computer languages. I'm
> nearly 50 and have 5 children - I'M
> NOT BRAGGING - I just need to stay employed - filePro has and
> does concern me - lets face it ...
> we haven't seen much change in 20 years, that doesn't work in
> this industry.
>
> (Opinion solely my own)
>
> Christopher Yerry
> CM Software
>


Not to keep this thread going.. but I'm compelled to by your opinion. :-)  I
think there has been significant change in filePro over the past 10 years.
The ability to build indexes on any fields saved it for me just exactly when
I *needed* it to be saved... at the 4.5 version.  Then, just as it was
becoming really problematic again, being able to DECLARE variables saved it
again at the 4.8 version. Those were significant enough for me to continue
using filePro and make our strong commitment to it. The 5.0 version has
added some nice features, many of which I use quite a lot actually, but it
was finally getting an ODBC interface that helped a great deal... though I
still have not relied heavily on it yet. Just the few things I've worked
over have been pretty good. I was hoping that the MEMO field from earlier
would give my programming a real shot in the arm, but  until they can be
printed... fully... this will have to remain a wish list item for me.

I do understand what you mane, though, the look and feel has not
significantly changed at all. Still no GUI which would have knocked down
almost all the barriers. There is fpGI, but it simply allows some mouse
interaction and no font sizing and other typical GUI functionality. I don't
really need this (yet...), so it isn't holding back any of my programming. I
think now, what would be really a lifesaver for filePro is a thorough XML
set of tools available in processing, and expanded MEMO functionality. The
next version (coming out shortly, I imagine) will already have 26 indexes...
so that is no longer a BIG wish list item. On the whole, I think filePro can
keep its loyal user base without any dramatic changes. Of course, a few of
those might be nice, too. :-)

John Esak

P.S. - Encrypting the now "visible" key/data storage would also be a big
plus.

P.P.S. And, how could I forget? A simple built-in mechanism for filePro to
pass data back and forth from web forms securely.  Maybe they should buy
Fairlight's OneGate and implement it internally... or even just RawQuery...
and build that into some functions. Making the web easier to use with
filePro is probably going to be a paramount factor in keeping filePro the
phenomenon we all know it to be.