Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.

Name:
Email:
Subject:
Message icon:

Attach:
(Clear Attachment)
(more attachments)
Allowed file types: gif, jpg, png, txt, tpl, lng, ini, pvd, psf, ini, cfg, csv, zip, xml, pas, 7z
Restrictions: 4 per post, maximum total size 1024KB, maximum individual size 1024KB
Note that any files attached will not be displayed until approved by a moderator.
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
How many words are in this question?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: rick.ca
« 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?
Posted by: deazo
« 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)?
Posted by: buah
« 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
Posted by: deazo
« 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.
Posted by: buah
« 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.
Posted by: buah
« 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]
Posted by: deazo
« 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.
Posted by: rick.ca
« 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.
Posted by: buah
« 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?
Posted by: rick.ca
« on: February 22, 2010, 03:11:47 am »

Yes, I can see it's clearly a database version problem. I suppose that's why the file is renamed with an "old" extension—the program is trying to update the file, but throws an exception because it doesn't recognize the newer version.

The question remains, how did it get that way? ???
Posted by: deazo
« on: February 22, 2010, 01:31:42 am »


 Rick,

 You can find my reduced database file here: http://hotfile.com/dl/22931781/2213196/NOS_FILMS.PVD.html

 It might help if you see if you can reproduce the problem on your side, or even examine the file.
 Remember to disable firebird services when you try to open it.

 
Posted by: rick.ca
« on: February 21, 2010, 11:10:07 pm »

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 thi8s problem and will let you know if I have some new info on the topic.

I don't understand. How did the format of his database get changed? I'm using Firebird Server 2.1.3 and have no problem using the same database with Firebird server or embedded. I suppose, if the database format for the two versions is different, the newer server version maintains the old for compatibility. But if that's the case, how did deazo's database get converted to the new format? Why am I unable to create a new database that exhibits the same problem? And is this a Windows configuration issue, a database format problem, or both?

I'm concerned we should be providing PvdImport users clear instructions on how to install and use Firebird Server, and perhaps a warning about about potential problems like this one.

I'm not sure it has any bearing on this topic, but I also suspect there could be changes made to PVD's Connect to server function that would make it more foolproof. Raldo made a change to how it's done on the PvdImport side, and that seemed to substantially reduce the number of problems users were having.
Posted by: buah
« on: February 21, 2010, 09:18:03 pm »

I'm sorry it didn't work. You should be able to export your database to an xml file. It creates "images" folder, and there's a colum with path to every exported image. Try this and export it to xml while having firebird files. Then uninstall PVD, open xml with MS Excel, save it as xls, install PVD and then try to import it to a new PVD database, with option "Save images to database" checked.
Posted by: deazo
« on: February 21, 2010, 06:54:42 pm »


 Buah I did try in the order you suggested and that did not change the problem.
 Neither the backup nor my database are opening with the current pvd17 version without adding the firebird 2.1 files.

 Nostra, thanks for having a look, I really do hope you will give me a way to sort that out and not have to use firebird 2.1 files.
 Just so you know, I can send you a reduced size database (10mb) (that behaves the same than my 600mb one) with which you can play if needed...

 
Posted by: nostra
« on: February 21, 2010, 06:07:14 pm »

I did not change anything regarding database engine in .17, so you must have done smth right :)
The conversion from an older version of firebird to the new one is a bit tricky and sometimes (should be seldom) can't be done automatically, so I am a bit afraid to move to the new version.
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 thi8s problem and will let you know if I have some new info on the topic.
Posted by: buah
« on: February 21, 2010, 03:58:22 pm »

Buah you are right, I had installed firebird 2.1 and not 2.5. If I am right this should be the only mistake I made, right?

It seems that you also uninstalled Firebird prior to uninstalled PVD. And I would clean registry of any PVD and Firebird references, restart the computer and than install PVD .17.

It has to be something with Windows, as Rick suspected.
Posted by: deazo
« on: February 21, 2010, 02:57:07 pm »


 Hang on....

 I think Nostra must have changed something in PVD17 because I copied Firebird 2.1 files in the PVD directory and I can now open my database !

 I can now open my database by using the old trick of placing 2.1 embedded files into the pvd directory.
 Don't know if that's what Nostra intended in version 17 but thank you anyway!

 Now still, I would like to be able to 100% fix this. What should I do in order to use PVD just as it is (without firebird 2.1 files) and my database?
 Can I export it into a new file that I could then open with PVD wihtout the firefbird 2.1 files?

 I hope this is not too messy and that we still understand each other...
 
Posted by: deazo
« on: February 21, 2010, 02:49:00 pm »

 OK I have redone everything and still get the error when restoring the backup.
 The only difference is that instead of "found 8" it says "found 9"...

 Do you know why?

 Just for info, I am using PVD17 now.
 
Posted by: deazo
« on: February 21, 2010, 02:39:28 pm »


 Buah you are right, I had installed firebird 2.1 and not 2.5. If I am right this should be the only mistake I made, right?
 I will try to install 2.5 and do everything again and post the results.
 In the meantime let me know if you think I missed anything else please.
 
 Don't worry about offense, I'd rather get offended and solve my problems!
 
Posted by: buah
« on: February 21, 2010, 02:12:05 pm »

Deazo,

I don't know what that error message means, but it's not SQL error any more, right? For now, what I'm able to conclude based on your last post is that you didn't follow step by step my previous post, meaning what version of Firebird to install, and in what order what and when to uninstall and install. Also, I would try fbembeded and fbclient files from Firebird 2.5 package.

Please don't be offended if you did all step by step, but I'm just trying to help here, and how you described it here I'm unsure of it.
anything