English > Support

Msvcr80.dll then Runtime errors...

<< < (4/6) > >>

deazo:

 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...

 

buah:
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.

rick.ca:

--- Quote from: nostra on February 21, 2010, 06:07:14 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.
--- End quote ---

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.

deazo:

 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.

 

rick.ca:
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? ???

Navigation

[0] Message Index

[#] Next page

[*] Previous page