Copy file1 to file2

[GCC Consulting]

> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com 
> [mailto:filepro-list-bounces at lists.celestial.com] On Behalf 
> Of Fairlight
> Sent: Sunday, June 13, 2004 12:46 PM
> To: Fplist (E-mail)
> Subject: Re: Copy file1 to file2
> 
> This public service announcement was brought to you by John Esak:
> > So how does Tony get 4.12???
> > I believe he has tried over and over and over. He also 
> actually bought 
> > 5.0, but wants to still keep using the 4.8 he has on his 
> first box. FP 
> > Tech has _two_ sales under their belt (not too mention the other 
> > people Tony buys product for...) So, how does he get the update for 
> > the first copy of filePro he bought?  Or, does FP Tech 
> actually think 
> > he only owns _one_ copy... which would be completely wrong. 
> He did not 
> > buy 5.0 to upgrade his 4.8 copy. He bought an entirely new, 
> 2nd copy of filePro.  What is the actual scoop?
> 
> Indeed.  And lest someone fall back on the, "That version is 
> no longer supported," excuse for the unavailability of 
> patches, I would remind them that Microsoft no longer 
> officially supports Windows 95, but you can still get all the 
> patches up to the EOL point.
> 
> IOW, that excuse doesn't hold water.  You can do a lot of 
> things to boost sales of newer versions.  Yanking the latest 
> updates to the major version someone is licensed for (after 
> an arbitrary date) and basically forcing them to upgrade to 
> get a working product is not one of the smartest methods, 
> IMHO.  Nobody's explicitly said it (that I can remember), but 
> that appears to be the case from what I've gathered from 
> several wishing to get
> 4.8.12 if they had 4.8.(N<12).  And I'm betting that EOL 
> notice was never given to them in advance, to boot.  I don't 
> remember any advance warning from -any- channel, official or 
> community, ever hitting this list.  It was noted after the 
> fact that only 5.0.x was supported anymore and 4.8 could no 
> longer be had.

Would someone with a copy of 4.8.(N=>12) be in violation of licensing for
supplying it to another, with a valid license, who didn't update to soon enough
and can't get the maintenance upgrade from fpTech directly?

Interesting question. 

Now I will say this, I had performance issues with native 4.8.10 and above which
disappeared with the 5.0 upgrade.

I had reports which had been taking just under 30 seconds to run thru 200,000
records with 4.8.3 take almost 30 minutes to do the same with 4.8.10.  I finally
rewrote the select processes, where I could, to use - lookups.  For those that I
couldn't, I ran rreport 4.8.3.  I renamed the program r3report.exe.

Is it necessary to upgrade, No, but many problems will be solved with 5.0.  I
still have an account running my brokerage app on 4.5 with no problems.
However, he can't upgrade to my latest version of the program as it makes use of
4.8 and 5.0 features.