Active State's distribution is always threaded.

Are you sure you have the MySQL table set up properly? Do you have the proper DBD::mysql installed?

The application has been in the works for over 12 months and the database has been working fine. About two weeks ago I did a release that used all hard coded or SQL::Abstract based SQL. It packaged nicely with PerlApp and built nicely into a setup.exe package using NSIS which delivers the database, installs it, and puts around 4.5 million records in the database.

My sin was to change what I was doing! I had a request for a major new feature addition. So I started a new module and I decided to use Class::DBI to get the flexibility with reduced coding time. From teh command line it works beautifully, but after compiling it with PerlApp - nix!

It seems that the thread issue is a red herring. By adding the --nocheck option to the PerlAppinvocation you can avoid the crash. The real issue seems to be module dependencies. Slowly - bit by bit, I am going through and adding use statements for the modules used by other modules. Each time things get a little better! It seems the real problem is that PerlApp is unable to find modules required by other modules!

Thanks for the suggestion, and for the opportunity to vent a little :)

jdtoronto