Moving filePro from SCO SYSV to Windows NT???

[Scott Nelson]

DJKnox at aol.com wrote:

> Hello all,
>  
> I've rarely written to the list so please excuse any etiquette issues.
>  
> We have a filePro system built on over 20 years of development, from 
> quotes, orders, inventory all the way through g/l as well as other 
> applications.  Estimated over 600 filePro files. Because of a 
> corporate directive, we are gradually moving to a Windows, SQL, VB 
> environment.  Some front-end applications have been developed in VB & 
> SQL and we are currently transferring information through flat files 
> several times a day using cron and other various methods.  Since 
> fpODBC is available, it is believed that if we can move all of the 
> filePro applications to the Windows version that it would be 
> beneficial.  Because the current applications, menus, scripts, 
> printers codes, etc., have been written around the UNIX environment, I 
> estimated a possible 1 year timeframe before we could completely 
> switch.  This was also based on maintaining the current UNIX system 
> and making sure the same additions/changes are done within the Windows 
> applications as well as testing. This would mainly be a one to two 
> person project.  I may be far off the mark on my time estimate (as 
> some feel), therefore, I thought if I could get any tips, suggestions, 
> opinions from the esteemed list it might be helpful.
>  
> The only benefit I can see in the move is that I might be able to keep 
> the filePro applications around longer if I can prove filePro and 
> fpODBC can work within the "Microsoft -Great Plains" environment.
>  
> Eventually, the corporate goal is, that filePro system would only be 
> used for historical purposes.
>  
> Any ideas would be appreciated.
>  
> Thanks,
> DeAnna Knox
>
>------------------------------------------------------------------------
>

Several options for "windowizing" filePro should be investigated before 
leaving a solid platform like SCO
for the undisputable problems with an ms server.

All of my clients are on SCO regardless of size.  To make filePro a 
graphical environment, I use web tools,
such as Apache, HTML Javascript, and FPWEB or fPCGI.   The power and 
security of the unix server
is maintained, and the workstations can be windows, linux or 
multi-console stations. 

Of course, you will see those that follow the ms way, and have few 
problems, but since you have experience
with the stability of SCO, I believe you will notice a difference if you 
change.  The same will hold true if filePro
is replaced with any other database tools. 

You should consider keeping filePro on SCO as the database and server, 
and use other tools to front-end
and odbc your data.

Hope that helps,

Scott Nelson
Logic Data Systems