Jeff Chahal Posted April 2, 2020 Posted April 2, 2020 Hi, I was scanning some comics in via the barcodes and I got this error. I've not done any manual input of dates, anyone have any idea what's going on? I've run through the fix procedure and it just comes back up. Thanks in advance.
Mark J. Castaneda Posted April 2, 2020 Posted April 2, 2020 Download/install the revised CB2020 installer (20.0.2.3198) from your online account here: https://www.comicbase.com/mycb/Registrations.aspx Start up CB2020 afterwards and see if things improve. Let us know how you make out.
Steven L. Dasinger Posted April 2, 2020 Posted April 2, 2020 No need unless you already have V3198 installed. Just install on top of the older version.
Jeff Chahal Posted April 2, 2020 Author Posted April 2, 2020 Still getting the same error when I start the software up. Ran through the fix and same result.
Mark J. Castaneda Posted April 2, 2020 Posted April 2, 2020 i'll reach out to our programming team for suggestions
Jeff Chahal Posted April 2, 2020 Author Posted April 2, 2020 Thank you, I have another friend in the UK that's tried the free version and is getting the same problem.
Peter R. Bickford Posted April 2, 2020 Posted April 2, 2020 Try using File > File Tools > Rebuild Lists > Item Information, using the current build (3198)
Jeff Chahal Posted April 2, 2020 Author Posted April 2, 2020 That's cleared it, any idea what the cause was?
Michael R. Wagner Posted April 3, 2020 Posted April 3, 2020 I encountered this error message and clicked "yes" to fix it. The software then updated every list and removed every date entry from my database - every date entry. It also removed every bit of data contained in one of the custom fields I use. The latter wasn't a date, but text identifying the location of the issue in my collection (Box001, Box002, Box003, etc.) I couldn't find any way to undo the changes, so resorted to deleting the database and opening the last backup version I had prior to receiving the error message. Had to reenter all the data I had put in over 48 hours or so, which was frustrating. The error hasn't reappeared since.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now