>We are converting from Foxpro 6 to Foxpro 8. When we run the program through the Foxpro 8 command window it works fine.
>When we run it outside the window it does not. THe code deals with table buffering. Does Foxpro 8 handle cursersetprop differently??

By 'outside the window' do you mean running it as an EXE or APP? Can we assume since this was working in VFP6, that you do have a properly placed READ EVENTS? If you did not use a READ EVENTS, was the initial form loaded at app launch time MODAL and now it is not? Can you better explain what it is that is not working? AFAIK, VFP does not handle cursorsetprop/buffering any differently between these versions. But again, I think we need more information about what is not working as you expect.

If you are wroking with SQL, then yes there was a change in how SQL runs which could affect any local views you have. See SET ENGINEBEHAVIOR in the VFP Help file for that. If you have any views where you have aggregate function in the field SELECT list (e.g., MAX(Field1), SUM(Field2), etc), then your SQL MUST have a GROUP BY expression for every non-aggregated field in that list unless you SET ENGINEBEHAVIOR 70.