Migrating filePro to Windows Server2003 ?

[Jeroen Elias]

One customer of the company I work for uses Terminal Services to do their
office work;
using Office applications like Word, Outlook, etc., and an intranet
application, and they use network printers scattered all over the LAN/WAN.
So, using Terminal Services might just be practical for you, if you set it
up correctly.

There might be a slight problem in your filePro code, and that is references
to file paths. On Unix systems, this normally will have the "/" character as
a directory delimiter, but on Windows systems, this normally would be a
backslash ("\").
Perhaps Windows is intelligent enough through all the years to understand
the original desired paths, but I don't know for sure.


Just my 2cents

Regards,
  Jeroen Elias - www.ccengine.com



----- Original Message ----- 
From: "Robert Haussmann" <haussma at nextdimension.net>
To: "'Jay R. Ashworth'" <jra at baylink.com>; <filepro-list at seaslug.org>
Sent: Friday, November 04, 2005 18:21
Subject: RE: Migrating filePro to Windows Server2003 ?


> > On Tue, Nov 01, 2005 at 10:53:45AM -0500, Dan Snyder wrote:
> > >    We  have  an SCO server v5.0.6 that is having serious
> > hardware issues.
> > >    We  have  about  35  users  accessing filePro on this
> > system.  We were
> > >    hoping the server would last until we migrated to a new
> > ERP system but
> > >    the  server doesn't look like it's going to make it.
> > Since we already
> > >    have several  Windows servers and support resources are
> > easier to come
> > >    by,  we  are  considering  migrating filePro to a
> > Windows 2003 server.
> > >    I'd  like  to  get  some  feedback  from anyone that has
> > migrated from
> > >    filePro on SCO to filePro on Windows.
> >
> [...]
>
> > >    How  do  client  workstations  access the windows
> > server?  Is it still
> > >    telnet or is it file sharing (we are using SCO
> > termvision right now)?
> >
> > Each workstation will access the key, data and index files on imported
> > filesystems -- it is *not* client server; you need to
> > appraise how much
> > traffic that's going to cause on your LAN and make sure you have
> > sufficient bandwidth.
> >
> > On the Unix side, the client is *on the same backplane* as the data;
> > that won't be true on a Windows network.
> >
>
> Just a clarification--Jay is referring to the default installation
> on a standard windows network.  That being said, there are ways to
> make the Windows implementation work in much the same was as the
> *nix one.  Using Terminal services, for example, the client would
> be on the same backplane as the data.  One could also use a
> telnet implementation and utilize the character-based filePro system
> directly on the server.  We using both types of solutions in different
> locations with very positive results.
>
> Bob Haussmann
> Tabor Children's Servcies.
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>