>I agree with you entirely Sergey. However, this app was originally written by two programmers over a course of 10 years. I am writing the VFP7 version and in the meantime, both versions need to share the same data. Also, mem files are used throughout the original app which consists of literally hundreds of screens and hundreds of prgs. I had many constraints placed on me in developing the VFP7 app, but when you change jobs after 7 years and join a new team, you live with it. The original programmers are still on board and want the mem files, so they get to keep the mem files. I am now low man on the totem pole so to speak! Ah, that's life!
>Tracy

Tracy;

Sounds like some of the places where I have worked. It is nice to have a job and it is also nice to have a life. Perhaps that is why I love flamenco guitar and other activities so much. At work we "count wigits standing on our heads using Base 12". The rest of the world uses Base 10. Who am I to disagree with management? :) As long as they give me my pay check they can do whatever they please. In return I will do what ever they please - well, almost. Everyone has his/her limits! :)

Tom

>
>>IMHO, there's something wrong with design of your application if you have to use mem files. You can store this info in the memo field or text file the same way VFP stores property values in the forms/classes or use a table with separate fileds for variable name, type and value.
>>
>>>We have tables that are shared between FPD26 and VFP6/7 apps that work fine if you use the set compatible command as well as set the codepage on the tables to 437 (MSDOS). (When we install the VFP6/7 apps we set the codepage on all of the tables to 437 before the app is opened the first time after the install). Tables created on the fly in VFP though must be copied to type fox2x for the FPD26 app to see/use them. The biggest problem though that I have not been able to surmount is memory files. If you save information stored in variables to a memory file in VFP6/7, the FPD26 app cannot access them. Perhaps someone has found a workaround for this? I don't want a separate directory for FPD26 mem files because they both need to open the same files to share the information.
>>>
>>>Tracy
>>>>It is true that fp2.6 an VFP7.0 dbf's are different. Only in header Microsoft pu a few simbols that set with what product you work.
>>>>My programmers tell me that if you open a DBF's with other version - it change header and could be not possible to open it with original one.
>>>>We refuse that kind of project where client like to work simultaneously modules done with FPW2.6 and VFP7.0