Working in Action Comics is Really Slow

[Jeff Schultz]

Whenever I'm entering data in Action Comics and hitting F3 to jump to an issue, it takes around 30 minutes before the issue becomes active to edit. What would be the reason for that? Action seems to be the only title that gives me trouble.

[Steven L. Dasinger]

What Edition (Archive, Pro, Express) and Version do you have?

Do you have your database on a regular harddrive or an SSD or something else?

The first thing I would try is menu item File->File Tools and use Rebuild Lists (checking all but the last one (unless you want the Picture files info updated).

Next, I would try Optimize Database using the last option Full Database Integrity Check...

If none of those work, you can try these tests:

A) Go to another Title with many issues (like Commando) and try F3.

If it works normally, there is probably something wrong with the data in Action Comics. If it is also slow, it might be your computer.

B) Use menu item File->New Database to create a new database, Run a Content Update on it, then test the F3 on Action Comics.

If F3 on Action Comics is still slow, it may be something with your computer. If F3 works normally, it is something in your database.

Either way, if Rebuild List or Optimize database do not help, you may need to contact support directly (email and phone number are on CB's website).

 

[Mark J. Castaneda]

Also... restart your computer to refresh your computer resources. May help. 

[Jeff Schultz]

Thanks for the advice, all. Ultimately it was a system issue because of the way I have things set up. I have both the database and pictures on an external drive so I can use it on both my desktop and laptop. I share that picture folder so I can map it as a network drive and then in File->File Tools->Manage Pictures, I set it to point to that mapped drive. On a whim, I copied the database and pictures to my laptop, and reset where the pictures are pointed too. That sped things up greatly. On my desktop, I set the picture path to where they are on the external drive (instead of the mapped drive), and that also sped things up.

[Jeff Schultz]

A final thought; it appears that a mapped drive is what slowed it up. There's no issue with speed when it's a direct path to the pictures.