Adam Sternberg

@Andrew d’Entremont, the livestreams also go up on YouTube; I'm unable to watch live as well, but I usually watch a day or two later on YouTube.

@Steven L. Dasinger, good memory! That was indeed me, and I do still have it. @Fred Slota, it's been several years since I worked on it, so it may need some tweaking and recompiling, but I think it still good. Caveat emptor, your mileage may vary, etc., etc., but if you're willing to be a little patient and give me about a week, I'll work on cleaning it up and posting it. (I didn't realize we had a downloads section in the new forums, or I'd have done this sooner!)

I've noticed some strange behavior with the update logs in build 21.0.1.1671 when updating content using Sidekick vs. within ComicBase itself. I have three databases that I maintain and update weekly through Sidekick. The update logs generated all have the name of the first database in the queue (which happens to be the default ComicBase Database.cbdb) in the log filename. However, when I update from ComicBase, the log has the name of the database open (in this case, Default ComicBase Database.cbdb) is in the log filename. The same also is true of the name of the database listed in the log

This (https://atomicavenue.com/atomic/item/953834/1/DC-Super-Hero-Girls-Holiday-Special-2019) should be removed in favor of DC Super Hero Girls: At Metropolis High HO 1 (https://atomicavenue.com/atomic/item/951870/1/DC-Super-Hero-Girls-At-Metropolis-High-Holiday-Special-1), which matches the indicia.

A good example of the problems that can be created is this past week's Die!namite #4. That issue (similar to other Dynamite and IDW comics) often have a cover gallery that will explicitly give a cover letter (Die!namite 4 lists "peanuts homage cover art" as cover H, but it wasn't listed in the database, and variant H was already used for one of the exclusives. In that case, I'll list the letter from the cover gallery in the notes when I submit, and leave the variant letter alone.

That's correct, if memory serves. I don't recall actual issue numbers, but there was a "quadtych" with those titles during the Millennium event. I have no idea about the Julianna Ferriter credit.

Mark, you may need to re-apply the update. Hold the SHIFT key down while kicking off the update until it actually starts and you'll be asked if you want to re-apply the update. It should pick up everything this time.

I was afraid you'd say that, but I totally get it. I'll change them in my copy of the data

Mickey Mouse and Friends 301/A is a single-issue example of this (I propose the issue really should be 301). https://atomicavenue.com/atomic/item/473217/1/Mickey-Mouse-and-Friends-301A

I propose that Donald Duck Adventures Take-Along Comic (Walt Disney’s…) FCBD 2003, FCBD 2003/A, FCBD 2003/B, and FCBD 2003/C should all be moved to Donald Duck—Free Comic Book Day (Walt Disney’s…). They were originally there years ago, and I'm not clear why they were moved. From https://atomicavenue.com/atomic/TitleDetail.aspx?TitleID=15122&M=1 to https://atomicavenue.com/atomic/TitleDetail.aspx?TitleID=22726&M=1

Before I submit these proposed changes, I'd like to get an ruling. I've seen at least one title that consists of nothing but variants. That is, all the issues are 1/A, 2/A, 3/A, etc. instead of 1, 2, 3, etc. The title I saw most recently with this is IDW's Walt Disney's Comics and Stories (https://atomicavenue.com/atomic/TitleDetail.aspx?TitleID=59697&M=1). Mark Castaneda, any guidance on whether these should be converted from variants to regular issues? Thanks

@Gregory Hecht, I'd had a similar problem in the past. I ended up deleting all the databases online as Mark suggested (note: NOT locally), and then only the ones I backed up or save reports for were there next time.

(I should have known! 😆)

I was afraid of that, but thought I ask those wiser than I. Also, allow me to apologize for being unclear. I didn't mean to imply/request access to the master database. I'd long ago created a new database and have done nothing with it other than to apply the weekly updates; that way, the database mirrors the master without being an actual copy. I was hoping there was some kind of database magic that could be used to compare the two, but it sounds like a resounding no, no way, better not post it! 😁 I'll play around with some methods and see if anything works nicely.

Steve, thanks for posting this. I have a related question. I have a "clean" database that I keep updated every week as a "copy of master" for easier reference. Can you think of a way to compare two databases (aside from exporting both into CSV and compare the two in a spreadsheet or text comparison)? Adam