Hi,
Hi,
I can't tell what error is being thrown without reverting back to the older code, as we have an intercept that generates a standard message. We have not had any problems with the Axolot-based code not being able to save - when it has run into incompatible features in an excel file it has saved a corrupted file instead of throwing an error.
Sorry, I am not aware of anything that could be causing issues. Maybe the fact that FlexCel doesn't currently save file properties could be causing the crash (if they expect file properties to be saved, even when they aren't required by the spec). But it could be anything else really.
I recovered the Axolot code and the error, which seems to occur only after the .xlsx file has been edited and saved using FlexCel, is "Unknown ID in workbook relationship".
OK, I have tracked down the crash and the cause, but not being an xlsx expert it means little to me. Maybe it does to you.
Thanks for the info. Indeed I think it helps. Actually when I saw the first message I think I already had figured out what was going on.
Just for the record, we' ve already added a new property "XlsxExtraCompatibility" that if you set to true, will use rID instead of flId for the relationships. Setting it to true will mean the possibility of some id clash with Excel's own ids in the future, but this is unlikely anyway, and well, this property should help you workaround this problem.
forgot to say, this property will be available in FlexCel 6, that if there aren't any other delays (which I hope there won't) will be available tomorrow.
Thanks for your prompt and detailed response. In my case, the only time this is an issue is when the user has two of our apps and has only updated the one that is normally run first, so that the file is first modified by FlexCel in the updated app and then attempted to be modified and saved in a non-updated copy of the other app. That actually would happen often because of the way the apps interact (the first calls the second under some common circumstances), but it is easily fixed by always requiring the second app to be updated when the first one is. The problem will go away, as the apps must be updated regularly to stay in compliance with the requirements that they help the user meet.
Hi,