upgrade form v0.98.13 to v1.0.16 ...::: DISASTER :::...

[SFX Group]

Hi

I never normally like upgrading as you end up with problems, although looks like ive been lucky lately UNTIL the above version.

I was already on .NET2 (that was minor issues), downloaded v1.0.16, also downloaded the MS C++ update do-dad as well.

1. Killed all running GBPVR and stopped service
2. Installed C++ update
3. Install v1.0.16, this failed and rolled back (this is where the problem starts)
4. Install v1.0.16 again, failed and rolled back.
5. Restarted PC (first time since doing any of this).
6. Install v1.0.16, now installed OK.

HOWEVER
Lost capture sources, KEPT the recording DIRs which i found odd and LOST the database with all recorded stuff in.

Heres where i am now, setup capture sources again, cleaned any plugins (Webcams2, Weather, EWA) these all work, still having problems with MVPTRAYICON but working on that now, think its an INI file issue.

The question is this, i NEED the database with all my recordings in, i have the files but need them to show in the READY directory.

I cant find a GBPVR.DB3 file (i have a super good backup system and its never been in there ever), however i do have the GBPVR.MDB and thats about 256Mb in size, but when i copy this over i get MVP crashes in the Recordings menu and the software doesnt work on the PC (get windowed database errors).

So was v0.98.x database compatible with v1.0.16?
Is there a way of pulling all these files in?
There physiclally still on the hard drive i just need them to show in the READY menu with the descriptions and times (girlfriend going to KILL me, this has been super stable since i started with it years ago... its early AM here now and cant go to bed till this works).

[fhmanas]

I believe 0.98.x was still using the Access database, sub has since moved on to using SQLite, there is a utility that sub included that would convert your Access data to SQLlite, look for ChangeDatabase.exe in your C:\Program Files\devnz\gbpvr folder.

[sub]

So was v0.98.x database compatible with v1.0.16?

No. The database file is never portable between versions.

Your best bet is to probably uninstall, delete the gbpvr directory, then reinstall your old version, and restore your database and config.xml from your backup, then try the upgrade again.

[SFX Group]

No. The database file is never portable between versions.

What about the above "change database" method?

If i installed another version on a different machine then copied the config.xml and gbpvr.mdb to that machine (being v.98.x) then made sure it worked, then upgraded THAT install to v1.0.16 then moved the config.xml and gbpvr.mb3 over to the current working v1.0.16 would do it then?

Is there not a tool (as mentioned above) that be used on the older gbpvr.mdb file alone that i can then just import (copy over) a file in the current working v1.0.16.

As the current machine is working on v1.0.16 i'm very reluctant to remove this install, however i can use another machine as a build to do any converstions.

[sub]

What about the above "change database" method?

No, thats just for switching from the old access database to the new DB3 file. It expects the files to be mean for the same version of the application.

If i installed another version on a different machine then copied the config.xml and gbpvr.mdb to that machine (being v.98.x) then made sure it worked, then upgraded THAT install to v1.0.16 then moved the config.xml and gbpvr.mb3 over to the current working v1.0.16 would do it then?

Yes, that should be fine but you need to make sure before copying config.xml/gbpvr.mdb to the machine that you set <AutoRemoveMissingRecordings>false</AutoRemoveMissingRecordings> in config.xml, otherwise you'll lose your list of ready recordings.

Is there not a tool (as mentioned above) that be used on the older gbpvr.mdb file alone that i can then just import (copy over) a file in the current working v1.0.16.

You can use the import recordings feature, or MpegImport on the wiki, to import your list of 'ready' recordings. You'd have to reschedule any season recordings etc.

[SFX Group]

I'm going to look at this, but it appears the new install wiped out the current database, it might have been 250Mb, but the backup is 1.5Gb, so theres a shed load of data missing, the backup doesnt like backing up open files (however the new backup version does do open files but thats to late now).

Will look at the tools on the WIKI though about this to see what i can salvage about it.

This problem is now closed, although no resolution was found.

[sub]

I hate to say 'I told you so' but... Its precisely for these rare type of upgrade problems that I always recommend people backup their database and config.xml prior to upgrading to a new version.

[SFX Group]

I hate to say 'I told you so' but... Its precisely for these rare type of upgrade problems that I always recommend people backup their database and config.xml prior to upgrading to a new version.

:p



While i'm here, i notice both SQL and ACCESS access methods are listed in the config.xml file, if you have created a DB3 file you then have 2 database files, how does GBPVR know which one to use, i assume you can delete one of them, question is how do you know which one its using (SQL (DB3) or Access (MDB))?

Which is the best to use? i would assume SQL, are you used an ODBC in the system already thats shipped with Windows 2000 (and above) to access the database or one you have written yourself that gets installed?

[-Oz-]

SQL is the best, fastests, smallest (normally), etc.

[sub]

While i'm here, i notice both SQL and ACCESS access methods are listed in the config.xml file, if you have created a DB3 file you then have 2 database files, how does GBPVR know which one to use, i assume you can delete one of them, question is how do you know which one its using (SQL (DB3) or Access (MDB))?

The config file tell GB-PVR which database being used. If you look at the settings in config.xml you'll see the examples for both databases are commented out, and only one is enabled.

If a user sets up a new system, then their config.xml starts out as a copy of config-master.dont-edit-me.xml, which will by default give them SQLite database settings.

Which is the best to use? i would assume SQL, are you used an ODBC in the system already thats shipped with Windows 2000 (and above) to access the database or one you have written yourself that gets installed?

We switched to SQLite to resolve some bugs with MS Access databases (ever growing files, and commited data not immediately available in the database which could cause several bugs in the app), so SQLite is definitely my preferred option. Every new install over the last year has been SQLite by default.