#56 Error 13 (Type mismatch) in procedure CompareWorksheets of Form frmMain

[Dan Moran]

I get this error message when I click the Compare button. Running version 1.31.0. I'm comparing nearly identical files and configuration settings as I did with the previous version which did not give me this error.
Let me know if you need more details.
Thank you.

[SteveT]

I can't reproduce the problem, so can you send me some files that generate
the error and your config file: %APPDATA%\Spreadsheet Compare\Spreadsheet
Compare Settings.ini

Thanks, Steve

---

This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com

[SteveT]

I believe I have found the problem (or another). While testing something else, I deleted all the stored sessions. With nothing loaded, the database compare was selected but with no primary key column. This generated the fault you saw.
I have modified the code. Hopefully this fixes your issue as well.

Steve

[Dan Moran]

Steve,
I'm sending you a pair of spreadsheets that I have this problem with along with the settings.ini file. I upgraded today to 1.32.0 but I get the same error with it as well. I deleted the one saved session I was using but that didn't change anything.
These spreadsheets contain three worksheets but I typically only compare the Data worksheets. I tried running Spreadsheet Compare again after deleting the saved session. This time I didn't exclude the other two worksheets from the compare and I got three identical error messages.
Also I only run the Full Compare and I thought I was getting valid results from the program (results were still being produced despite the error message). I deliberately made a change to one of these spreadsheets in the Data worksheet but the Full Compare said no changes were found. When I ran Quick Compare, it correctly pointed out the change.
Let me know if there is anything else I can provide to assist you with debugging this error.
Thank you.
Best Regards,Dan

[SteveT]

Thanks. Looking at the ini file, I see that the database compare column is
blank as I suspected. I will download the files, but if you enter a number
of signify the database key column, you should find everything works okay.

Steve

---

This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com

[Dan Moran]

Steve,
Thank you. This worked. Perhaps that setting was filled in by default in version 1.30.0 (and earlier versions I assume) or else I filled it in and it had been retained in the saved session; I'm not certain because it was filled in when I reverted back to 1.30.0. Anyway, it is working and I know now to check that the key column has an entry.
Much obliged for the help.
Best Regards,Dan

To: 56@bugs.spreadshcompare.p.re.sf.net
From: stevetowner@users.sf.net
Subject: [spreadshcompare:bugs] Re: #56 Error 13 (Type mismatch) in procedure CompareWorksheets of Form frmMain
Date: Thu, 20 Mar 2014 23:36:48 +0000

Thanks. Looking at the ini file, I see that the database compare column is

blank as I suspected. I will download the files, but if you enter a number

of signify the database key column, you should find everything works okay.

Steve

This email is free from viruses and malware because avast! Antivirus protection is active.

http://www.avast.com

[bugs:#56] Error 13 (Type mismatch) in procedure CompareWorksheets of Form frmMain

Status: pending

Group: Current_Version

Created: Wed Mar 19, 2014 09:27 PM UTC by Dan Moran

Last Updated: Thu Mar 20, 2014 08:54 PM UTC

Owner: nobody

I get this error message when I click the Compare button. Running version 1.31.0. I'm comparing nearly identical files and configuration settings as I did with the previous version which did not give me this error.

Let me know if you need more details.

Thank you.

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/spreadshcompare/bugs/56/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Dan Moran]

Steve,
FYI: I reverted back to version 1.30.0 and it is working correctly, detecting the change that 1.31.0 and 1.32.0 did not catch with Full Compare.
Thank you.
Best Regards,Dan