-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ignore custom / unknown functions #26
Comments
+1 I have some excel functions implemented in VBA that are called in some cells and I get the same failure message. |
Sorry somehow this slipped my notice. If you're still facing this - can you attach an example spreadsheet? |
I am having the same problem with a VBA user defined function used in one of my workbooks. Although I cannot reproduce it with another workbook. Is it possible to print out more information about which cell the error is related to? So I can track down the offending formula. |
Hmm ya I can probably add cell to the failure message, good suggestion. Meanwhile can you try running it with --debug flag? It might give some hint. |
I got this message:
|
I just published a release https://github.com/na-ka-na/ExcelCompare/releases/download/0.6.1/ExcelCompare-0.6.1.zip which would print the cell information. Can you try that? |
Thanks. I tried it out and I have found that the only way to fix that problem is to goto the cell, place my cursor in the formula bar and press enter (I think effectively entering the formula again). I cannot fix the cells by doing a recalculation by pressing Ctrl + Alt + F9. It seems that the cells with the UDF in the formulas have found them selves in a strange state (possibly Excel bug? I know, presumptuous, but I have come across many bugs in Excel). I still cannot seem to replicate the problem with another workbook :/ I thought it may be my use of VBA-IDE-Code-Export, but I tried various actions with that and cannot reproduce it. I tried to search to see if others have had the same problem but didn't find any solutions. Not a problem, I think I'll pass on using ExcelCompare for this project. I may use it for others where I can start using it from the beginning so I know when this problem starts. A possible solution for this problem might be to read the cell's formula instead of evaluating the cell's value. That is probably a better implementation anyway since you are then reading the actual authoritative content of the cell rather than a consequence of the content. (I am assuming the cell's formula is being evaluated based on the stack trace). |
Actually it is just reading (parsing) the formula, not evaluating it. I
don't evaluate formulas. It is failing to just parse the formula.
…On Jan 29, 2017 10:14 PM, "Matthew Palermo" ***@***.***> wrote:
Thanks. I tried it out and I have found that the only way to fix that
problem is to goto the cell, place my cursor in the formula bar and press
enter (I think effectively entering the formula again). I cannot fix the
cells by doing a recalculation by pressing Ctrl + Alt + F9. It seems that
the cells with the UDF in the formulas have found them selves in a strange
state (possibly Excel bug? I know, presumptuous, but I have come across
many bugs in Excel).
I still cannot seem to replicate the problem with another workbook :/ I
thought it may be my use of VBA-IDE-Code-Export
<https://github.com/spences10/VBA-IDE-Code-Export>, but I tried various
actions with that and cannot reproduce it. I tried to search to see if
others have had the same problem but didn't find any solutions.
Not a problem, I think I'll pass on using ExcelCompare for this project. I
may use it for others where I can start using it from the beginning so I
know when this problem starts.
A possible solution for this problem might be to read the cell's formula
instead of evaluating the cell's value. That is probably a better
implementation anyway since you are then reading the actual authoritative
content of the cell rather than a consequence of the content. (I am
assuming the cell's formula is being evaluated based on the stack trace).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAQBhBlKecwQSmwoNfonbU_sel2x1ZTxks5rXX_MgaJpZM4Fp68M>
.
|
Ah, my mistake. Judging by the description here https://poi.apache.org/apidocs/org/apache/poi/ss/formula/FormulaParseException.html, I'll have to ask Apache POI about this issue if I want to figure it out. |
It would be interesting to see if openpyxl or Open XML SDK has the same issue. |
I'm trying to diff two spreadsheets that were created with google spreadsheets. In them I use a number of google docs specific functions such as REGEXMATCH which fails the diff with
Diff failed: Name 'REGEXMATCH' is completely unknown in the current workbook
The text was updated successfully, but these errors were encountered: