I put the following message in a support ticket 2 months ago but as I haven't received an answer yet I thought I might ask on the forum, too.

For a while the program has been crashing when I was working with it At first you could still make it run by using the repair utility but now even that does not work- Once the program crashes when restarting you get to the screen where you can choose whether to run a normal startup or a diagnostic startup. With both alternatives the program does not start unless you start a new database. I have reinstalled the program several times and restored the backup both from my personal backup file as well as from the DVD Profiler online collection. The program either doesn't run at all or it crashes after I updated a few profiles. This began with the previous version (3.9?)  and was carried over to version 4.0.

As this error occurs on three different computers (with either Windows 7 or Windows 10 - one of them brand new) in the same way I suspect that the problem lies within my collection. The complete collection runs up to collection number 9999 with approximately 14.000 entries.

As a test I cut my collection in 2 parts with part one containing collection numer 1 to 9500 (because I didn't have any major problems before I passed that number) with a little over 12.000 entries. This collection seems to run OK.

The second part contains collection numbers 9500 to 9999 with some numbers missing in between. While this collection is fairly small the program crashed again. Even after repairing this database it will not load.

This leads me to believe that the problem has to do with the collection numbers themselves. I did not find anything on the technical forum that dealt with a similar subject.

I would really appreciate your help to fix this problem. I just don't think there's a better program out there for handling a film collection.

One thing you could try is to backup the current database, create a new blank database, and restore into the new database. See if you can open the new database without error. This has been known to fix some errors.

Food for thought:

This will take lots of time, but it is low risk.

(1) Export the collection to XML
(2) Start with a new, clean database and use BulkEdit XML Import to rebuild. Since BulkEdit was designed to bring in data from multiple sources, it will sometimes sanitize broken data. Not much to lose. Just let it run overnight. The fewer columns you select for display, the faster it will run. If the import hits a bug, and I fix it, You can always rerun after the bug fix. (sentence corrected)

If you are not familiar with BulkEdit, I suggest practicing on a small test file. If you ever need to interrupt a long-running import process, just click on the progress bar.