I am using VS 2005 and VB.Net to build a simple Windows application with a local JET (Access) database.
During development the Database.mdb file is located in my Debug directory, so this is where I pointed the source for my crystal reports. Naturally everthing is working just fine on my development system.
I published my new application (after setting the active build configuration to Release) and have successfully installed it on another test system. The application works fine until I attempt to use the crystalreports viewer. As soon as I do a Database Login dialog box is displayed and no matter what I try to put in the username and password textboxes (including nothing at all) the login fails.
It is probably significant to note that I have not implemented any security passwords or features in the local database.mdb file.
I suspect that rather than being a security problem, this is really being caused by my reports not being able to find the database file.
How do I solve this problem?