Jump to content

Matthew P. Plassman

Members
  • Posts

    28
  • Joined

  • Last visited

Recent Profile Visitors

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

Matthew P. Plassman's Achievements

Apprentice

Apprentice (3/14)

  • First Post
  • Collaborator Rare
  • Conversation Starter

Recent Badges

0

Reputation

  1. Worked for me, too. Thank you for fixing this so fast!
  2. Yes, sir. Thank you.
  3. Sorry, I always forget some bit of information. I'm using Archive. I'm sorting new comics into my collection, so I'm changing the value in my item custom field of "Storage Box" for items shifting to a new box. I've done this every month for years without trouble. For example: I did a Find search for items in Storage Box "8." I selected the comics that were shifting to a new box, hit Ctrl+G like always, and I got the error message. However, when I got out of Find and just went to a regular title page, like Fantastic Four, I selected one item, hit Ctrl+G, things worked perfectly. I selected multiple items on that page, hit Ctrl+G, things worked perfectly. So I ran the Find results again, but single selection or multiple selection, I still get the error, so it's only a problem when I'm trying to do a change on the results of a Find search. I hope that makes sense. I feel like I often try to explain things and fail to make anything clearer.
  4. Just to check things off the "to try" list: also just got the build 1228 update - also did not fix the problem.
  5. Minor update: this only happens when trying to make a Quick Change on results for a Find search. If I try Quick Change in the usual database listings, I receive no error.
  6. I'm getting the attached error when trying to perform a quick change. I tried quitting and restarting the program. I tried optimizing. I tried rebuilding all the lists. No luck. I'm running v25.0.0.1220 on Windows 11. Is this an uninstall/reinstall situation? Thanks.
  7. That did the trick. Thanks!
  8. I have a pretty basic setup. Just one monitor. My settings are for the screen saver to turn on after 10 minutes, the screen to turn off after 20 minutes, and the computer to go to sleep after 3 hours. I update Windows and drivers at the beginning of every month. Nothing's changed with my computer from the time between the screen saver still working and it stopping to work. I don't think I've even added any new programs. Oh well. Just wanted to check in on it. If the screen saver is my only issue with the program, I can live with that.
  9. I have recurring issues with Sidekick and error messages, but I have historically been negligent in capturing them. Well, that has changed! I caught one of my nemeses tonight! While Sidekick runs the database update, it likes to tell me that I must update my database by opening ComicBase before Sidekick can use it? It soldiers on through the error message, though, but gets stuck in a never-ending update loop. ComicBase is not currently open as this is running. My computer is running Win 10, and my CB version is 23.2.2.2744.
  10. My computer begs to differ. Still broken for me with build 23.2.2.2744. I'm willing to concede this is somehow something specifically wrong with something on my end.
  11. I'm having the same issue with my screensaver, but I've also been having a lot of technical issues with CB as of late (regular Sidekick errors, database not linking to the mobile app, phantom database on my online account). I'll be emailing support shortly. As an added note on this issue, though, when I check the screen saver dropdown menu, I have both "ComicBase Cover Gallery" and "PComicBase Cover Gallery" listed as options. If I select the latter, it defaults to the former. "PComicBase" also disappears if I switch to a Windows screen saver, but reappears after I switch back to the regular "ComicBase Cover Gallery" screen saver and check the drop down again. For now, it's back to the old Windows Photo slide show.
  12. And please disregard that resubmission I just sent of issue 2803. I had been updating the issue details this morning and didn't realize you had already made the adjustments I had requested. Thank you for your prompt updating.
  13. Also, just got off the phone with the publisher's customer service. I can confirm that the Summer 2022 issue was the final issue. Sci-Fi Magazine is no longer in publication.
  14. Hey, it's me again to revisit everyone's favorite topic, seven months later. A little housekeeping to adjust the most recent issues. What you currently have as 2704: Please delete. This entry is listed as being "September 2021," even though an issue for that month already exists (see 2703) and the cover is a duplicate from issue 2605. According to the indicia, then, the three most recent issues need to move a number: The Winter 2022 issue (Eternals cover) should be 2704 (not 2801, as currently listed) The Spring 2022 issue (Star Trek: Picard cover) should be 2801 (not 2802, as currently listed) And the Summer 2022 issue (Obi-Wan cover) should be 2802 (not 2803, as currently listed) And as the fall issue is waaaaaaaay overdue, maybe that will be the end of this title, and there will be no further occasion for the editorial team to curse my name.
  15. And here are those 3 covers I promised for 2301, 2304, and 2506.
×
×
  • Create New...