Well, not really a "guru", but I seem to be one of the few that is still actively working with ACCPAC source products (SBT).

3.2 to 6.0 is a _major_ jump. Isn't 3.2 written in FPW? I haven't worked with it, but I took a peek in the tech ref and there are references to screen generators. If that's so, you're not only dealing with the changes in Pro series; you're dealing with the jump to OOP, however badly it's implemented in Pro. :)

My best advice to you would be to get the specs of the mods and just do them in 6. I wouldn't try to reuse the code. Keep in mind that I haven't looked at the code for 3.2, but if it is in FPW, I can't imagine that it would be a straight port. Especially if there's any mods to the screens that are now MDI.

If it were me, I would use the oportunity to improve the mods with the new tools available in VFP6. If it took a month to move from 3.0 to 3.2, there must be a lot of mods. (Unless they were really different Pros, I guess... I'm trying to give advice in the dark since I started with Pro 5.0. :) ) This would be a good chance to see if you can lessen the footprint of the mods in the Pro code. 6.5 is due out this summer and will have a _lot_ of changes. If the mods are too intertwined in the source, you could end up having to do a lot of work to move them again.

I don't know of any white papers or FAQs about porting, but John Kiernan's site has good info about Pro programming in general. [ http://www.kierpro.com ] If you have reseller access, I would suggest joining the Loop, even if it's just the basic access. [ http://www.accpacloop.com ]

If you have any specific questions, feel free to email me. [ michellec@softserv-inc.com ]

Michelle


>Hi Michelle,
>You seem to be the SBT guru in UT.
>
>My previous company has contracted me to help move all their modifications to the latest SBT version.
>Last time, from 3.0 to 3.2, it was straight forward.
>I compared unmodified 3.0 to modified, then found the same code point in 3.2 and applied the same modification. This took about a month.
>
>This time, I do not even know if the same menu item calls the same named code.
>
>Do you know of any white paper, hints, FAQ's about porting modifications from SBT 3.2 to 6.0? I have access of a reseller, but I am not on the "Loop".
>
>TIA