Rick,

>The manual indicates we must do this manually. Do we need to create a new test project with the old project's name to get QuickStart to generate the new ADATAENV.VCX (and associated MMDATAENV.*) to get started? In other words, do you have a step-by-step account of the best way to do this conversion?>

You can simply create a new ADataEnv.vcx using the CREATE CLASSLIB command, then edit your business objects with the builder to create new data environement classes / cursor objects for the bizobj. I am looking at a conversion utility given to me by BOb Archer this week that I may be uploading for others to use.

I haven't had a minute to check it out yet, but I simply need to check if his conversion utility builds the DE / cursor objects as a composite class rather than separate classes for DE's and cursors.

>Also, I noticed a problem when editing a data environment's custom methods. When I added code to PostInitHook (to create an index on a view), then went back to add additional code to the method, the original code did not appear in the editing window.>

This problem is addressed in the new MM 4.0 Service Pack 1. See my message in this forum for download details.

Regards,