>problem
>
>- I have a database in vfp 3.0
>- I open it in vfp 5.0 (I put datas in the files)

this solution is a SEVERE hack ... but i have never had a
problem when using it.

be careful with this solution ... you are playing with dynamite.

First of all open up the .dbc file as if it were a table with
a "USE" command.

the .dbc file is really just a table with a very special format.

one of the fields in this table is "objectname"

look for a row that is not deleted and has "storedproceduresobject"
in the field "objectname".

now go into the memo field called "code".

delete the contents of this memo field.

inside that memo field was the compiled object code version of what is inside
the "code" memo field of the row "StoredProceduresSource".

you can now open up the database in either vfp3 or vfp5.

However, if either version recompiles the stored procedure code located in the "code" memo field of "StoredProceduresSource" then the database can only be opened in that version.

You will need to find out ... in the software you have made
and in the daily use of the database what actions will trigger
a recompilation of Stored Procedure Source code.

like i said this is a real HACK around the problem but i have not had any problems doing it ....
i recommend backing up the database files before erasing the contents of memo fields.

HTH Dave.