Message
From
28/09/2006 10:47:45
To
28/09/2006 04:53:31
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Title:
Re: 30Update.prg
Miscellaneous
Thread ID:
01157498
Message ID:
01157849
Views:
53
>Hi,
>
>>>Someone just asked me to look at a VFP database corruption problem...
>>>
>>>When attempting to open the database in the project manager I get the following error:
>>>
>>>This file is incompatible with the current version of Visual FoxPro. Run 30UPDATE.PRG to update the file to the current version.
>>>
>>>Only reference I could find to this is at http://support.microsoft.com/?id=200025 but only in that it details it as a spurious error message. None of the other factors apply (i.e. no multiple executables or ADO or the Visual FoxPro ODBC involved - and it's not VFP6.0)
>>>
>>>FWIW this database has never been near a VFP3.0 environment but I think that's a red herring anyway.
>>
>>Maybe a file has been corrupted in such a way that your current version of VFP (which is it?) thinks it's a 3.0 file.
>
>That's what I thought. AFAICT the DBC design changed between the beta and release versions of VFP3 and 30UPDATE.PRG was provided to make the conversion. I figured that if I could find out what changes were made (a copy of 30UPDATE.PRG should show that) I'd have a clue about where to look for the problem in the DBC. The DBC opens OK as a table BTW.
>
>>Besides the usual database/table/index suspects you might want to look at your FOXUSER resource files (perhaps rename them to see if that makes a difference).
>
>I'll check but the same error occurred in three different environments (the user, initial tech support guy and my own) so I don't think it will be a factor.
>
>Regards,
>Viv
Greetings,
Just a thought... perhaps you could open up a valid DBC as a table and compare it to the DBC that will not open to see if you can uncover a distinction between them. I'm stating the obvious but you should probably back up the files before changing them to try and get it working.
Greg
>
>>>Someone just asked me to look at a VFP database corruption problem...
>>>
>>>When attempting to open the database in the project manager I get the following error:
>>>
>>>This file is incompatible with the current version of Visual FoxPro. Run 30UPDATE.PRG to update the file to the current version.
>>>
>>>Only reference I could find to this is at http://support.microsoft.com/?id=200025 but only in that it details it as a spurious error message. None of the other factors apply (i.e. no multiple executables or ADO or the Visual FoxPro ODBC involved - and it's not VFP6.0)
>>>
>>>FWIW this database has never been near a VFP3.0 environment but I think that's a red herring anyway.
>>
>>Maybe a file has been corrupted in such a way that your current version of VFP (which is it?) thinks it's a 3.0 file.
>
>That's what I thought. AFAICT the DBC design changed between the beta and release versions of VFP3 and 30UPDATE.PRG was provided to make the conversion. I figured that if I could find out what changes were made (a copy of 30UPDATE.PRG should show that) I'd have a clue about where to look for the problem in the DBC. The DBC opens OK as a table BTW.
>
>>Besides the usual database/table/index suspects you might want to look at your FOXUSER resource files (perhaps rename them to see if that makes a difference).
>
>I'll check but the same error occurred in three different environments (the user, initial tech support guy and my own) so I don't think it will be a factor.
>
>Regards,
>Viv
Greetings,
Just a thought... perhaps you could open up a valid DBC as a table and compare it to the DBC that will not open to see if you can uncover a distinction between them. I'm stating the obvious but you should probably back up the files before changing them to try and get it working.
Greg