Author Topic: Msvcr80.dll then Runtime errors...  (Read 23657 times)

0 Members and 1 Guest are viewing this topic.

buah

  • Guest
Re: Msvcr80.dll then Runtime errors...
« Reply #20 on: February 22, 2010, 03:28:51 am »
For me it says:
Quote
exception message : Specified file is not a Personal Video Database XML file.

Did you get the same message in bug report?

Offline rick.ca

  • Global Moderator
  • *****
  • Posts: 3241
  • "I'm willing to shoot you!"
    • View Profile
Re: Msvcr80.dll then Runtime errors...
« Reply #21 on: February 22, 2010, 04:41:33 am »
I did. I assume that's coming from the routine that thinks it's going update the database to a new format.

Offline deazo

  • Older Power User
  • *****
  • Posts: 283
    • View Profile
Re: Msvcr80.dll then Runtime errors...
« Reply #22 on: February 22, 2010, 08:25:12 pm »

 I did not get the error message you are describing actually (Specified file is not a PVD XML file), unless you are looking at the bug report, which I did not read in details.

buah

  • Guest
Re: Msvcr80.dll then Runtime errors...
« Reply #23 on: February 23, 2010, 12:37:05 am »

 I did not get the error message you are describing actually (Specified file is not a PVD XML file), unless you are looking at the bug report, which I did not read in details.

... in bug report?

I was thinking if you changed your template somehow...

[still stubborn to find a solution]

buah

  • Guest
Re: Msvcr80.dll then Runtime errors...
« Reply #24 on: February 23, 2010, 10:44:26 am »
Deazo, why wouldn't you try to export old one then to import to a new database, like I suggested earlier? It'll take 2-3 hours, if not less.

Offline deazo

  • Older Power User
  • *****
  • Posts: 283
    • View Profile
Re: Msvcr80.dll then Runtime errors...
« Reply #25 on: February 23, 2010, 03:21:11 pm »

 Yes Buah I noted your suggestion.
 My problem is that I am away from home for one week so I cannot do it right now. But yes I'm actually looking forward to trying that one out.
 Can I ask you, do you think I should export/import with the same pvd version? And I guess between exporting and importing I should unsinstall/reinstall pvd, right?
 I'll let you know how it turns out.

buah

  • Guest
Re: Msvcr80.dll then Runtime errors...
« Reply #26 on: February 23, 2010, 04:41:46 pm »
Ok, here's what I'd do if I were you.

0. I'd make a backup of an existing database.
1. I'd save images externally (uncheck this option in Preferences)
2. I'd export database both to xml and csv, while having Firebird files embedded and with older version of PVD.
3. I'd uninstall PVD, and clean registry, and restart computer.
4. I'd install new version of PVD with unchecked option "Save images to database"
5. I'd import csv, or xml.
6. I'd follow this procedure to import images.

Cheers

Offline deazo

  • Older Power User
  • *****
  • Posts: 283
    • View Profile
Re: Msvcr80.dll then Runtime errors...
« Reply #27 on: February 23, 2010, 06:39:44 pm »

 Thanks,

 wouldn't this mean that my posters would be "locked" outside of the database file?
 Or can I then re-integrate them into a database file (the way I prefer them to be)?

Offline rick.ca

  • Global Moderator
  • *****
  • Posts: 3241
  • "I'm willing to shoot you!"
    • View Profile
Re: Msvcr80.dll then Runtime errors...
« Reply #28 on: February 23, 2010, 07:51:49 pm »
Quote
3. I'd uninstall PVD, and clean registry, and restart computer.

This won't hurt, but I don't believe it will accomplish anything. PVD doesn't install system files or make any changes to the registry.

Quote
Or can I then re-integrate them into a database file (the way I prefer them to be)?

Yes. That's buah's step 6. This is necessary (and a brilliant idea) because the export/import routines are for text only.

I do not know if there is an easy way to convert your database back to 2.03 (used in PVD), but I'll investigate this problem and will let you know if I have some new info on the topic.

If I were you, I'd wait and see if nostra has more to say. I'd also like to know how/why this happens in the first place. You don't want to go to the trouble of rebuilding your database, only to have the same thing happen again. Also, what are the implications for your database when Firebird embedded is ultimately updated?