Moving filePro from SCO SYSV to Windows NT???

[GCC Consulting]

	From: filepro-list-bounces at lists.celestial.com
[mailto:filepro-list-bounces at lists.celestial.com] On Behalf Of DJKnox at aol.com
	Sent: Wednesday, September 29, 2004 10:35 AM
	To: filepro-list at lists.celestial.com
	Subject: Moving filePro from SCO SYSV to Windows NT???
	
	
		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
	
One of the advantages to moving to FPODBC is that it can "front End" an SQL
database.  This might make management "happy".  You could stay with your current
app in filePro and they can use all the SQL Windows centric tools they want.
Just a thought.

The other advantage to keeping fpodbc around is that you can use fp to run
custom reports which may not be available easily through SQL queries against the
SQL database.

Richard Kreiss
GCC Consulting