If an imported custom data file has the same name as a default SilkPerformer data file, upon closure and reopening of the SilkPerformer project, the data file will revert to the default SilkPerformer 2011 Data file. Possible Workarounds to this issue: a) Give the custom data file a different name to the files listed within the default data folder b) Delete the pre-existing data file in the default data folder c) Manually reference the data file within your script by using the FileFixedLoad() or FileCSVLoadGlobal() functions. An example of the issue, if you refer to screenshot A and B. Screenshot A, shows that we have included a custom data file called 'Airports.csv' from a location outside of the SilkPerformer environment. SCREENSHOT A However, when closing and re-opening the SilkPerformer project, you will note that the Data file has now reverted to the 'Airports.csv' data file listed within the SilkPerformer Data Folder. SCREENSHOT B For further information on the functions listed as workarounds, FileFixedLoad() | FileCSVLoadGlobal(), refer to the SilkPerformer 2011 online help (SilkPerformer | Help | Contents). Also for a full list of data file names and types held within SilkPerformer 2011 refer to C:\Users\Public\Documents\SilkPerformer 2011\Data (this location may differ based on Operating Systems and installation path chosen). Incident #2557427 Old KB# 35847 Created On: 20 April 2012
↧