>>Thanks for the WAGs. It turned out to be classes.dbf; excluded from the project, it never made it to the new location. The Domain Admins could see it in the original directory.
>>
>>Any idea why that's excluded by default? Or what it'll break if I include it?
>
>I've never run into any problem by compiling in the classes.dbf file. I think the idea behind excluding it is to allow you more flexibility. You can do things like customizing versions of your app. on a per-customer basis by simply shipping them a different classes.dbf. Your app. includes all the functionality by default, but instanciates different classes for each customer. Maintaining the table is a lot simpler than compiling a different version.

True. I just don't have enough hair left to find out the hard way that I've left out some file or another from the "release" version.