Moving filePro from SCO SYSV to Windows NT???

[DJKnox at aol.com]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.celestial.com/pipermail/filepro-list/attachments/20040929/e8de555a/attachment.html