Article ID	2400
Article Title	INFO: Why did some of my files not get migrated (when upgrading to DataFlex 12 and higher)?
Article URL	http://www.dataaccess.com/kbasepublic/KBPrint.asp?ArticleID=2400
KBase Category	Visual DataFlex
Date Created	11/18/2008
Last Edit Date	06/18/2020

Article Text
DataFlex has Migration Wizards that are automatically invoked if you open a workspace from a prior revision of DataFlex. The wizards analyze the workspace's code and attempt to migrate as much as possible of the workspace's code to the current DataFlex revision.

Sometimes the results of the migration are unexpected. This article will try to shed some light on the types of issues that have been reported to us.


ISSUE: Some components (e.g. views, dialogs) are not migrated.

In order to migrate properly, all components must be parsed in the context of a project. So, if there are components that are not used in any project in the workspace, they won't be considered for modification by the migration wizard.

The reason for this is as follows:

Most source code files reference code in other source code files. For example, creating a view with some dbForm controls and Data Dictionary Objects (DDOs) in it will need to reference the classes these controls are instantiated from. These are defined in other files. When you have a DataFlex project (an application) that compiles and runs, we know (or assume, at least) that all references in that project are present.

This is the same idea that is applied in the "current project" concept in the Studio. You can read more about this in the DataFlex help in the Workspace Explorer help topic.



This article is recommended reading for the following keywords and/or categories:
migration upgrade
Contributed By:
Dennis Piccioni
Company: Data Access Worldwide
email: dennis@dataaccess.com
Web Site: http://www.dataaccess.com


Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2024 Data Access Corporation. All rights reserved.

The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.