>HI all.
>
>I have an app which is half MM, and half...well...not-MM. It's been a bit of a headache maintaining, especially when migrating to clients.
>
>In the next week or two, I'm going to take the final plunge and go 100% MM components, just to simplify life in the long run (it better!).
>
>The app consists of one MM form which is heavily used (say 30% of total app usage), another non-MM form which is more heavily used (say 50% of total), and about 20 other forms, all not MM. I'm using a VFP backend. I'm launching everything from my own framework, which means I've had to jury-rig things to get the MM stuff to work.
>
>I have to make a few decisions, and I'd appreciate advice/help thinking them through:
>
>Decision 1: How to migrate existing forms, business objects into the full MM application.
>I see three options, not all viable -
>1) Totally rewrite (not an option);
>2) Redefine my forms as subclasses of the basic MM form, cross my fingers, run it, and try to get things working;
>3) Leave my forms as they are, and just call them from within MM. They mostly use my home-made 3-tier framework, but some call data directly. My home-made forms and biz objects don't care about their environment, other than they need to have the folder hierarchy to the data maintained (this might be the easiest to prototype/test). My concern here is in registering these forms with MM without native MM functionality. This concern relates almost entirely to the process of exiting the app.
>
>Decision 2: What to do about the project.
>I see 2 options here:
>1) Start with a new project. I've made so many tweaks and modifications to MM to get things to work, I feel like my best course of action is to just start a new MM project, and bring in my existing data. I can't imagine what I might have broken during the process, and I have no idea the extent of my changes.
>2) Try to fix things up in the existing project. I've gotten very deep into MM to get things to work to this point, but my knowledge of it is still not complete, so I worry about some deeply hidden things I may have broken, meaning I'm not psyched about this option.
>
>I appreciate any advice any one can give on either of the above decisions!
>
>Thanks,
>
>David


David,

I could write you a book on doing this because I've gone through it before. The problem you are going to face is taking advantage of upgrades. I know you say that a total rewrite is not an option, but actually it may be your best option. If you bite the bullet now, you won't have to fight the framework for the rest of your life. A lot of very careful thought went into the framework design, and basically you have created a hybrid from the framework. This will give you headaches down the road.

So, here is my advise: Start a brand new project and bring in your data. One by one start converting your forms. Use the set classlib option to call the forms that have not been converted in your old project until you have completed the whole thing. If you need further information feel free to write or call.

Jim