Jump to content

Fred Slota

Members
  • Posts

    398
  • Joined

  • Last visited

  • Days Won

    4

Fred Slota last won the day on March 4

Fred Slota had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Fred Slota's Achievements

Community Regular

Community Regular (8/14)

  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges

8

Reputation

  1. Tried to submit, and while I assume the database entry with "Wraparound Cover" as "Item Description" was submitted, it did not react to my cover scan...
  2. Second issue with the issue... The indicia reads "Cain", not "Caine"...
  3. I'm not sure what the proper way to enter this title *should* be, but I think the way it is currently entered looks... odd... Electric Black, The Children of Caine, The ???
  4. You misunderstand entirely... Not saying it's a user problem... More a realization that there are multiple users, with multiple different opinions on what they want, and a solution that simultaneously supports both a fixed official title so CB can update official entries, with official descriptions and valuations, and a flexible alternative/addition set of fields that supports as many different users' views on how to name, group, sort and describe, would satisfy most users.
  5. Been a proponent of maintaining paired Official/User fields for the database with different display/reporting options Official Title and User Title Official Alphabetization and User Alphabetization Official Notes and User Notes Official Item Description and User Description Display choice/Report choice - Official, User, Official [User] or User [Official]
  6. But, of course, that requires one to properly match your understanding of which type of item you are scanning with how it is currently entered in ComicBase...
  7. Okay, it happens... A comic title gets entered with a wrong punctuation, or the title is changed between solicitation and publication, or a particular oddball book get's entered as one thing, but later reevaluation moves it as another. And so, new titles and issues are added to the official database, old titles and issues are deleted from the official database, and the content updater ripples these additions and attempts these subtractions, leaving many users who already entered inventory into their databases with unrecognized titles and issues. Okay, yes, we have the report of unrecognized titles and issues to help us find the orphans, but it's then a process of finding each new title, verifying each matching issue, and then transcribing your quantities, custom fields, grading notes and possibly other information. Suggestion - add a numeric Migration field. Each migrated old and new issue will have a unique Migration number assigned to it, negative for the old and positive for the new.. When the updater tries to delete an old issue, if you have inventory and the updater can't delete the issue, then the negative Migration number is added to that issue's Migration field. The software can now add a feature to search the database for negative Migration numbers and their matching positive Migration numbers. This could be used to generate a list or report that shows which old issues you have and where they should be moved to. Better still, this could be used to produce a ComicBase tool that shows these pairings, let's you review them, select from them, and automate the migration of your inventory from old entries to new entries. And you can select which other fields to copy over with the quantity; custom fields, grading notes. With a little behind-the-scenes work, this tool could even cross the ComicBook/Book/Magazine divide and help with the shifting of entries across those categories as well. I would imagine this system would not be backfilled with historical information about older issue migrations (although that would be increasingly helpful for people who haven't reconciled their unrecognizables), but going forward I'd guess this would be very helpful. I would also suggest that this tool also open the Unrecognized Items list, for those issues that won't be supported by Migration numbers.
  8. Add an option to auto-generate a Wanted Report when Sidekick Save to Cloud. Add support for Wanted status, or Wanted lists, to the other existing reports. Item Checklist already has "List only wanted issues", but what about filtering on or reporting status of Wanted issues for Collection Overview, Collection Report, etc.?
  9. Thanks Mark, but, that's what I did on 4/26, when I was first told Crystal Reports had a problem. And that resolved the problem. And then I installed the newest update, and it broke again. Are you not concerned that this has happened? Is there anything I can look at and report back to help with understanding how it is broken and how it happened? I thought that this was a recently resolved issue and was not expected to happen with current updates?
  10. So, I've been playing around with an Excel Workbook to find Holes. In the process of, about a week ago I went to update my Cloud Saved Wanted report, and was told there was a problem with my Crystal Reports. I didn't think anything of it, as there had been recent discussions about this problem, so, I followed the directions, uninstalled, removed SAP CR, reinstalled, and everything was happy. I produced a new Wanted Report, saved it to the cloud, with a 4/26/2022 date. A couple days later, through Check for Updates, a new version of ComicBase was found, 22.0.2.1680. I installed this. I noticed that during the update, it said it was doing something with SAP CR. I didn't think anything of it at the time. With the help of my Excel tool, I started adding some Wanted issues. I then decided to generate a new Wanted report. I am now, again, being told that there is a problem with Crystal Reports. This is 5 days and 1 CB program update after I had successfully repaired Crystal Reports. Before I go through the process of uninstalling/reinstalling, is there any other advice you could give or information you would want to know?
  11. I'm working on an Excel-based tool to support Hole Hunting, similar to Adam Sternberg's Collection Hole Finder. Ultimately, the goal is to update the Wanted status on issues in ComicBase, for Wanted List Reports and AtomicAvenue Wish Lists. The intended flow is Output from ComicBase a CSV Item Checklist of Owned and Missing issues in Owned Titles Load Item Checklist data into the spreadsheet Generate a listing of missing issues in holes Research/decide which issues in the listing you want/don't want on the spreadsheet Update the Wanted status of issues in ComicBase. Additional Research/decisions of which issues you want or don't want in ComicBase There are two features that I don't think are in ComicBase currently that would streamline this process. Add an option to include "Wanted" as a field included in the Item Checklist. (I could copy Wanted to a Custom Checkbox and output the Custom Checkbox, or I could generate a separate report of Only Wanted issues, but the ability to directly output Wanted Status would simplify the process.) Add an Import option that doesn't effect Quantity, but can Set/Clear Wanted, Marked or Custom Checkbox state for issues.
  12. Why does the first fail to generate a report, while the second does? By my reckoning, shouldn't the two methods produce identical output?
  13. So, I can generate an Item Checklist, of Missing Items, that I have checked as Wanted. How about an Item Checklist of unwanted Missing Items?
×
×
  • Create New...