Antiquated Software

[John Esak]

Well, I have written everything you mentioned, in filePro, for Nexus. All
the accounting, front-ends, back-ends... et al. When I need to interface to
Web stuff, usually PHP, it is always a custom job, and generally very
limited. It does work... but on the whole, I agree with you that filePro has
very little to offer that helps integrate any of our system to Perl. That
would be pretty nice if their was an API to the engine/indexes... (I think
that is coming in future releases). I'm afraid we are stuck with things as
they are now. I can only agree with you on your decision, staying with a
product that doesn't handle your needs would be crazy. (I wish my systems
were generic enouht to resell, but they aren't.)

Yes, we've been beta-testing 5.6 for a couple months mow. I think it is very
near release... I'll make comments after that happens.

John

P.S. - We are only two-tier (by your descrition... we don't do retail), but
we do have *everything* else a company our size needs working under
filePro... from the simplest quote on up through full EDI PO/Invoicing...
everything flows automatically to the G/L. Manufacturing on East and West
coast all tied together, many outlying offices... the whole ball of wax. I
would *never* say, though, that it has been easy. Writing and maintaining
this system to current needs has been a full time job for 20 years. Now it
takes two full time people (and several other support personnel) to keep it
all working and growing. I'm not sure if it would be any different with main
stream programs... I don't (at this point) have the need, desire (and you
might say luxury) to find out. We are constantly looking at other options,
the main one being FoxPro... however, why not leap right over that next
obvious platform and jump right into SQL Server... the prospects are
endless, but so are the learning curves and ramp-up time. It may happen for
us too, someday... I really hope it doesn't have to go that way... and not
getting certan "must-haves" in a reasonable time period is certainly going
to bring us to the same point you are now. While there is a chance, however,
we, at least, can keep up the hope.

> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com
> [mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of Walter
> Vaughan
> Sent: Monday, January 16, 2006 11:00 AM
> To: filePro
> Subject: Re: Antiquated Software
>
>
> John Esak wrote:
>
> > P.S. - by the way, not being able to print memos is a very big thing I
> > fully expected to see in 5.6 and I don't think it's in there yet.
>
> So I am guessing from a previous message that you are beta
> testing 5.6, and from
> what I can tell the *only* functional change is that key or data
> segments can be
> larger than 2 gigabytes on Operating Systems allow such.
>
> I have just got back from our long range strategy meeting, and it
> looks like the
> end of the line for filePro for core operations. I may end up
> using OBDC for
> reports, but I cannot keep the Vandals from invading Rome. I
> tried to fight, but
> I can no longer bet my career that using filePro is more
> important than what
> everyone else wants from our systems.
>
> Unless someone has a full ERP/MRP/CRM/Accounting system with 2
> direction GL
> visibility (view by product/category or sales campaign/channel)
> written in
> filePro for a three tier company
> (manufacturing/wholesale_distribution/retail)
> that will inter operate with php and perl directly (using similar
> api's as a sql
> database), then on March 31st we will issue a PO for a new
> platform, and our
> days with filePro will be winding down by the start of July 1st.
>
> --
> Walter
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list