PC Client - Throws an SQL exception if the share name can't be found

[HarryH3]

Sub, while setting up a PC Client on a Win 7 system, connecting to an XP Home server, I discovered that a misspelled share name causes NPVR to throw an SQL exception on startup. If you click "Continue" then the server and share settings show as blank. I ended up fixing the name by editing config.xml, but less technical users might not know to do that. Just wanted to let you know in case some code to capture and handle the error could reduce future install questions.

[sub]

You should already have got a message box saying "Server database not found at: \\servername\sharename" when you accessed the first thing that looked at the database (like TV Guide), but it probably went on to have an ugly error after that. I changed it so the application will terminate after this message. It is a critical error, and there is no way for it to operate without the database.

[HarryH3]

The conundrum that I see is that the user has to have NPVR running before they can fix the broken setting, but NPVR won't run because of the broken setting. Is there another way to get to the "Settings" screen? Perhaps I'm just missing something. In GBPVR the user could open config.exe and make changes without PVRX2 running first.

[sub]

You can start the app to the main menu, and right click to settings before this problem happens. If you'd clicked on TV Guide, or Recordings, then you'll see the message and the app will terminate.

[HarryH3]

I went back and intentionally recreated my error. Here's what happens on my system:

I intentionally left a letter out of the Database Share name. When I then started NPVR on the client, I got the message "Server database not found at \\Server\share\npvr.db3"

I clicked "OK" and the app opened. I right clicked and selected "Settings".
As soon as I click on "Devices" I get:

Unhandled exception has occurred in a component in your application. If you click Continue, the applications will ignore this error and attempt to continue.

Unable to open the database file.

If I then click continue, none of the installed devices are shown and the Server Name and Database Share are also blank. The "Act as client PC" checkbox is also no longer selected. I can go into config.xml on the client and see the settings there, but the app seems to lose contact with config.xml once the database error happens. Manually editing the correct name into the config.xml lets me get into NPVR just fine. It's not a big problem for me, but it could frustrate new NPG3VR users.

[sub]

You'll be able to do it in the next release. I tested the exact scenario you're describing numerous times this morning after I made the changes. You're using the old version that doesnt have the changes.

[HarryH3]

Aha! Just trying to make life easier for you. Can't wait to start playing with the next release!