Hi all,

Does anyone out there have any experience or knowledge about the ramifications of taking VFP8 vcx's and moving them back to VFP6 ( or VFP7)?

We recently ran into issues that prevent us from moving to VFP8 (documented elsewhere). Fortunately, these issues surfaced before we had implemented any VFP8 specific enhancements. Unfortunately, we have been using VFP8 for several months making extensive changes to our codebase to support new data structures, etc. The changes we made in the VFP8 environment were changes we would have made in the VFP6 environment and are fully compatible from a property, method and function call standpoint. We did use some of the tools such as "Code References" to identify requred changes and to actually make the changes, but again, these changes were compatible with VFP6 from a language standpoint. To make a long story short, we had not yet implemented any VFP8 specific property, method or function call changes.

On Monday, we moved our entire codebase back to VFP6 and put conditional compilation code in for any VFP8 specific functions calls, etc. So far, the code apppears to be solid, the application executes reliably as it did orignally under VFP6 before we moved to VFP8, but I am still slightly concerned that something might be in there that will cause a problem....a timebomb waiting to go off!

My experience with .vcx class libraries is fairly extensive and I do understand the structure quite well. I have not been able to find any potential problems and feel that if there was a problem, a full compile would identify it. In addition, every object in the application has been opened and visually reviewed!

My question is does anyone know of any reason why this would cause us (serious) problems? Has anyone identified any potential issues? Anybody out there move their code base from VFP7 back to VFP6 when show stopping bugs were identified?

Thanks in advance!
Bob