Starting out

Joe

Administrator
Staff member
Read through the code to find commonly reused items. These I translated first and wrote tests to be sure they worked. Including:

1. Error logging to a txt file
2. Connection opening/closing w SQL Server as well as ExecSelect(), ExecUpdate(), in the same connection object. These were functional translations rather than line-by-line.
3. Dot h file replacements like CRLF (Strings.CRLF - see ...)

I also found it helpful to outline the code at the Fox function level. Tools/DocumentView is particularly helpful in Fox. My outlines look like this:

ObjectName
1. Function1()
2. Function2()
____A. Function3() called by Function2
3. Function4()

I pick the most embedded functions, translate them, test them thoroughly and work my way back to the left margin.
 
Last edited:

Joe

Administrator
Staff member
Following the execution path was helpful to me. I found an entry point, translated it and went on from there. Some functions didn't need to be translated because they were never used or had become obsolete. The launching code was helpful as this was for daily launch business processes. Everything branched out from there. That got me busy fast.
 
Last edited:
Top