>>>>>Just to add. After MODIFY STRUCTURE, INDEX, PACK or setting the code page of FP 2.6 table in VFP it still can be opened in 2.6.
>>>>>However if you open FP 2.6 table in FP 2.5 and PACK it (when there are deleted records in the table) it will loose the code page info. But that's another story. :)
>>>>
>>>>The main reason for introduction of 2.6 so fast after 2.5 was the introduction of codepages. At least from my POW :).
>>>
>>>Yes, that's what mean. I work now on kind of funny application, where VFP 6 app uses FP 2.6 tables. FP 2.5 tables could not be used because they do not have codepage setting. But other parts of the project, handling the same 2.6 tables, run under Foxpro 2.5. I know it is stupid, but that was the corporate decision :) On several occasions other programmers were PACKing the tables in FP 2.5, which naturally resulted in loss of the code page.
>>
>>So what did you have to do? Run CpZero from YourOpenTableMethod each time cpdbf() returns zero? You may be lucky if you're dealing with just one codepage... :)
>
>I had to tell them not to use PACK. :) Another funny thing is that no records supposed to be deleted in those tables at all. :)
>
>>
>>Why did the chicken cross the road?
>>It had no idea. It was a corporate decision.
>
>Yeah, it was a corporate decision to build that road right across that farm. :)

Nick;


Corporate decisions allow for many needless meetings, which justify inept management, and allow for finger pointing sessions. This is an excellent form of exercise and is management’s most creative moment. Decision makers are an interesting lot. I have worked with companies that actually asked questions from those who had experience to solve specific problems. This has been a mixed bag as sometimes the correct solution is applied and at other times it is avoided. It just depends upon how big a “Golden Parachute” the decision maker has! :)

Some people in management should not be allowed to manage even an outhouse. They will do nothing but cause a stink. :)

Tom