I cannot seem to find any evidence that this should be a version specific issue, but at first glance, it appears that way. Let me first point out I was able to correct the issue for now on an adhoc basis, but I'd like to prevent it from happening in the future.
Here are the different details that I am aware of:
[ul][li]xls file created from a "template" - I use "template" loosely because thus far we have not used actual template files here - something I hope to change one day.[/li]
[li]When the file was opened on a machine running Windows 7 and Excel 2010, the UDF showed values correctly in cells where used.[/li]
[li]When the file was opened on 3 machines each running Windows 10 and Excel 2016, the UDF showed #VALUE.[/li]
[li]I corrected the immediate issue by selecting one cell involved in the calculations for each row of data and saved the file (using Windows 10 and Excel 2016).[/li]
[li]The calculations in the UDF previously were correct in some instances, and I corrected the UDF sometime in the last 6 months.[/li]
[li]The code in the UDF produces no errors, just does not always show values for some reason? (It does at each opening since I last corrected it as mentioned above).[/li]
[li]I found the mention of the Application.Volatile line that can be added to UDFs, but I am not certain that by itself would correct the issue.[/li][/ul]
Any ideas as to what would cause such an issue, and what the best methods to correct it would be?
"But thanks be to God, which giveth us the victory through our Lord Jesus Christ." 1 Corinthians 15:57
Here are the different details that I am aware of:
[ul][li]xls file created from a "template" - I use "template" loosely because thus far we have not used actual template files here - something I hope to change one day.[/li]
[li]When the file was opened on a machine running Windows 7 and Excel 2010, the UDF showed values correctly in cells where used.[/li]
[li]When the file was opened on 3 machines each running Windows 10 and Excel 2016, the UDF showed #VALUE.[/li]
[li]I corrected the immediate issue by selecting one cell involved in the calculations for each row of data and saved the file (using Windows 10 and Excel 2016).[/li]
[li]The calculations in the UDF previously were correct in some instances, and I corrected the UDF sometime in the last 6 months.[/li]
[li]The code in the UDF produces no errors, just does not always show values for some reason? (It does at each opening since I last corrected it as mentioned above).[/li]
[li]I found the mention of the Application.Volatile line that can be added to UDFs, but I am not certain that by itself would correct the issue.[/li][/ul]
Any ideas as to what would cause such an issue, and what the best methods to correct it would be?
"But thanks be to God, which giveth us the victory through our Lord Jesus Christ." 1 Corinthians 15:57