By setting DataAutoCellTypes to False, using the statement below, our issue disappeared. This lead us to the DataAutoCellTypes method, which by default is True.
#Fontcase windows pro#
This code works but it gave us the false assumption that this "type" wouldn't be overridden by any other logic.Īpparently this assumption turned out to be somewhat incorrect as it seems like cells with a certain value intermittently have their changes suppressed, as mentioned above with True/False. Some Popular Collection and Storage Programs Mac OS: FontExplorer Suitcase FontAgent Pro Fontcase Windows: Suitcase Fusion Typograf FontExpert Advanced Font.
#Fontcase windows windows#
When you double-click a file to open it, Windows examines the filename extension. TextCellType txt = new TextCellType() į = txt The VAULT data files are related to Fontcase. Part of this logic involved setting the CellType for all columns to TextCellType, example below. In our solution we are doing a lot of cell formatting prior to binding.
After looking at additional instances of published code it turns out that this issue is somewhat intermittent, but it seemed to be fairly consistent when cell values equal True or False. Also the dataset bound to the control has "CaseSensitive" set to "true", as noted in the screenshot below: Changing the value to something completely new works as expected.Īs mentioned prior this only happens when hosted in IIS. As you can see the case was preserved and not altered.Īgain this only happens when the user tries to change the case of the cell value. For example if the user tries to change a cell from "Click" to "click" the "HasChanges" condition will evaluate to "true" however, the value remains "Click."īelow is a screenshot where the user attempted to change a cell value from "False" to "false". The only problem is the value doesn't reflect the change the user made if that change involved changing the case. The code above works as expected, it detects the change and makes it to the "DataTable changes" statement. If (((DataSet)FpExcel.DataSource).HasChanges())ĭataTable changes = ((DataSet)FpExcel.DataSource).GetChanges().Tables
There are no problems with the code detecting changes however, there is a problem with the result returned.Įxample Code: public static DataTable getUpdatedGrid(FpSpread FpExcel, DataTable beforeDt) If changes are detected we then pull out the cell values where a delta exists.
We have some logic that checks for changes in the Datasource which has been bound to the FpSpread control. I'm able to debug this problem while attaching to the running IIS process ID from Visual Studio on the web-server. It does NOT occur when hosted through IIS Express (v.2.1) on my local machine. The problem below ONLY occurs when hosted in IIS from our web-server.
0 kommentar(er)
