Some customers encountered situation that the "Import Text“ node is not able to load the input file, when user loaded old version workspace (e.g. 13.0, 13.2) in a new version (e.g. 13.3). The user has to manually open the import text node and re-specify the input file path in order to run the workspace smoothly. 




This is due to the reason that the path to the input file in the new version 13.3 does not match the one specified in the old version Import Text node. If the input file is located in the same location/path when the workspace is loaded in the different version (e.g. a machine with 13.3 installed), the import text node is able to load the input file automatically. The user would not need to take extra effort to manually edit the node. 

For example, a 13.2 workspace with import text node to load the input file located at path C:\Users\lliu5.TULSA\Desktop\Adstudy_UTF8.csv.
When user copied the 13.2 workspace to a machine with 13.3 installed and executed the 13.2 workspace in version 13.3, the user has to check and make sure the input file is located in the same location in version 13.3 machine, that is, the input file is also located at path named C:\Users\lliu5.TULSA\Desktop\Adstudy_UTF8.csv in 13.3 machine. In such way, the user does not need to manually open the node and re-specify the input file path. 

This is important when user has many existing old version workspaces with import text node, and user does not want to re-edit each workspace after upgrading Statistica or moving project databases. 

Import Text node is able to remember input File path and load input file when old version workspace is opened in 13.3, as long as the input file has the same file path in the two versions of Statistica.

Windows 7, Windows Server 2012 R2