>Yes, the simpler the better. However...
>
>I'm concerned about the default value unique 'iid' fields not getting incremented/assigned properly if I APPEND or INSERT INTO the MM tables myself rather than using a business object. Is this a legitimate concern? What MM procedure library do I need to SET in order to assure that the NewID() method/function on the unique iid fields default value functions properly? I've not had time to try it yet, but would the StartMM.PRG be sufficient?

Yes, what I've done is setup NewID() as my field's default value. Then issue StartMM(). Then SET PROC TO MyConversionFunctionLibrary.prg (procedural file with a function for each table name... to go way overboard here, I set these procedural files up like a Chain of Responisibility design pattern), then I fire off which ever functions from that prg I need to run right from the command window or sometimes use a wrapper program if I have need to convert stuff in batches.

When you eliminate BizObj's from this picture, you dont need the extra calls SetX.prg, StartMM() is enough. HTH.