Windw 10 - Home

[Richard Kreiss]

There are more issue then just PFCMARK which was set to 30 a while back.

1. Menus options not working - when using a batch file (F5) option what ahs worked for years, it now doesn't work. (fixed by using the complete path to the fp folder.
2. No records selected when option is run.
3. Date selection has had to be corrected even with PFCMARK set properly and the indexes rebuilt. (Would like to upgrade this client to 6.0 and make use of the selection set option for Auto Indexes.)

I am playing "Wack-a-mole" with this client as I fix one thing and then I am advised of another issue or the thing I just fixed stops working.


Richard Kreiss
GCC Consulting



	

> -----Original Message-----
> From: Filepro-list <filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com>
> On Behalf Of Richard Kreiss via Filepro-list
> Sent: Wednesday, January 22, 2020 6:52 PM
> To: FilePro List <filepro-list at celestial.com>
> Subject: Re: Windw 10 - Home
> 
> Pfcmark was set to 30 back when the Y2K version was issued. I had already
> accounted for the century. Chang back in 1992. My programming mimicked
> what pfcmark does.
> 
> The issue arose after the November up date to Windows 10.  Home seems to be
> the problem not filePro. The programs run and print properly on my system.
> Win 19 Enterprise and server 2012 R2.
> 
> Richard
> Sent from my iPhone
> 
> On Jan 22, 2020, at 5:42 PM, Wayne Smith <smittyusn1 at gmail.com> wrote:
> 
> 
> Be sure PFCMARK=set to 30 or higher  on those machines running FP local and
> using the server drive.
> 
> Maybe's ...LOL
> 
> Wayne Smith
> 
> 
> On Wed, Jan 22, 2020 at 5:07 PM Richard Kreiss via Filepro-list <filepro-
> list at lists.celestial.com<mailto:filepro-list at lists.celestial.com>> wrote:
> I have a client who purchased 3 new computers with Windows 10 Home and
> migrated filePro to the one machine which is acting as a server(Not a lot of
> access).  They are on filePro 5.0.  and had no problems with the application for
> almost one year.  In December they started to have issues with filePro.  Menu
> scripts didn't work and some reports based on dares did not run properly and the
> Owner had problems printing reports to his local printer.
> 
> When I checked his system, I found that the print output got to the print spooler
> for this local printer but took over 10 minutes for it to start to print. When an
> output printed, it did print properly based on the print codes sent.
> 
> As anyone else seen problems with Windows 10 Home when networked?
> 
> I have recommended he upgrade to Windows 10 Pro or Enterprise to eliminate
> any network issues which may have been closed with an Update of Windows 10
> HOME.
> 
> After that I would like him to upgrade to filePro 6.0 so he can output PDF file
> directly.
> 
> 
> Richard Kreiss
> GCC Consulting
> 
> 
> 
> 
> 
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: winmail.dat
> Type: application/ms-tnef
> Size: 11984 bytes
> Desc: not available
> URL: <http://mailman.celestial.com/pipermail/filepro-
> list/attachments/20200122/469999c3/attachment.bin>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com<mailto:Filepro-list at lists.celestial.com>
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 
> 
> --
> Wayne Smith
> Port Orange, Florida
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.celestial.com/pipermail/filepro-
> list/attachments/20200122/ef7c6615/attachment.html>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list