fpcopy problem

[Mike Schwartz]

     I've run into the same thing, and it turned out to be an old version of
fpCopy that was lurking in the system and executing, instead of the fpCopy
that was in the fp executables subdirectory.  

     Check the date stamp that is on the fpCopy that is in your fp
executable subdirectory, and, if the version is current, search all your
other subdirectories to find the older version that is executing and rename
the older copy or get rid of it.

     Also, if you turn PFVER on, you should be able to tell which version of
fpCopy you are running.

Mike Schwartz

> -----Original Message-----
> From: filepro-list-bounces+mschw=athenet.net at lists.celestial.com
> [mailto:filepro-list-bounces+mschw=athenet.net at lists.celestial.com] On
> Behalf Of Robert T. Repko (R Squared Consultants)
> Sent: Tuesday, June 09, 2009 3:33 PM
> To: filepro-list at lists.celestial.com
> Subject: fpcopy problem
> 
> Every year I run fpcopy to roll over specific databases for the next
> year.  Every year fpcopy does not copy over a number of files (prc,
> out, sel, brw).  I could never figure out why they were not copying
> until now.  Would someone  fpcopy a filepro database that has file
> names of 11 characters or larger in their filepro name (by filepro
> name I mean the name excluding the prc, out, sel, ....  and let me
> know if the files copied to the new database.  It looks as though all
> the files that are not copied by fpcopy have a filepro name that is
> 11 characters or larger.
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.339 / Virus Database: 270.12.58/2164 - Release Date:
> 06/09/09 05:53:00