Filepro dlowdown

[John Esak]

Any chance of "rolling back" the upgrades since then?  It probably is
impossible, but it would be interesting to see if it actually made the
problem go away.
 

> -----Original Message-----
> From: Rkreiss at verizon.net] [mailto:rkreiss at verizon.net] 
> Sent: Monday, December 14, 2009 5:22 PM
> To: john at valar.com; 'gcc consulting'; 'Filepro List'
> Cc: filepro-list at lists.celestial.com
> Subject: RE: Filepro dlowdown
> 
> Yes - after an OS update around Thanksgiving.
> 
> Richard
> 
> -----Original Message-----
> From: John Esak <john at valar.com>
> Sent: Monday, December 14, 2009 4:42 PM
> To: 'Rkreiss at verizon.net]' <rkreiss at verizon.net>; 'gcc 
> consulting' <rkreiss at gccconsulting.net>; 'Filepro List' 
> <filepro-list at lists.celestial.com>
> Cc: filepro-list at lists.celestial.com
> Subject: RE: Filepro dlowdown
> 
> I don't see how the processing could affect this problem at 
> all.  And as you
> say it works fine reocrd to record and when you have 
> different connection
> types.   I know I would always like to run on the server like rdp'ing
> (terminal services) into the server and working rather than 
> dragging stuff
> back and forth to local machines of course. But you know 
> that, so no help
> there.  Did this just start happening?
> 
> John 
> 
> > -----Original Message-----
> > From: Rkreiss at verizon.net] [mailto:rkreiss at verizon.net] 
> > Sent: Monday, December 14, 2009 4:28 PM
> > To: john at valar.com; 'gcc consulting'; 'Filepro List'
> > Cc: filepro-list at lists.celestial.com
> > Subject: RE: Filepro dlowdown
> > 
> > John,
> > 
> > The problem is most pronounced with the locally attacted 
> > computers.  This is less of a problem when running from 
> > Terminal server.
> > 
> > The terminal server is mapped to the database server through 
> > a gigabit connection.  The local machines are connected 
> > through a 100 mb switch.
> > 
> > I have a lot of processing running in auto processing on the 
> > file which takes the longest to exit.  Could this cause such 
> > a lon delay?
> > 
> > This processing runs very fast when accessing a record.
> > 
> > Richard
> > 
> > -----Original Message-----
> > From: John Esak <john at valar.com>
> > Sent: Monday, December 14, 2009 4:20 PM
> > To: 'gcc consulting' <rkreiss at gccconsulting.net>; 'Filepro 
> > List' <filepro-list at lists.celestial.com>
> > Cc: filepro-list at lists.celestial.com
> > Subject: RE: Filepro dlowdown
> > 
> > I saw this exact symptom one time... Years ago... But it was 
> > when I tried to
> > mount an NFS filepro directory.  Never tried it since.  I'm 
> > sure youre not
> > doing that... But is it possible your developmer menu has 
> > access to the
> > correct DNS and the user menu doesn't?  
> > 
> > John
> >  
> > 
> > > -----Original Message-----
> > > From: filepro-list-bounces+john=valar.com at lists.celestial.com 
> > > [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
> > m] On Behalf Of gcc consulting
> > > Sent: Monday, December 14, 2009 4:13 PM
> > > To: Filepro List
> > > Subject: Filepro dlowdown
> > > 
> > > Windows Server 2008
> > > Client - Windows XP
> > > 
> > > After a Windiows XP update around Thanksgiving, my client has 
> > > noticed a conciderable slowdown when filpro exits back to the 
> > > menu from *clerk.
> 
> 
> [The entire original message is not included]
>