We've got a tool for saving V8 models back to V7 .dgn files. The approach uses the mdlWorkDGN_ functions with a CopyContext. There is a difference between the V8 model resolution and global origin and the V7 resolution and global origin. We account for that by scaling and shifting the contents. When we need to save out a V8 model, we create a V7 file and set it's "model" global Origin and working units to our V7 standards then close the file. Next we re-open the V7 file, scan the V8 model, and save the elements (after scale/translation) back to the V7 model. When a 2D file is processed, everything works fine. When a 3D file is processed, we get the V7 output file with the elements correctly scaled (based on the V7 working units) and in the correct location. However, when we check the V7 global origin, it reports a global origin that is NOT what we need it to be. We've tried both setting and not setting the V7 model's global origin, but every time we open the .dgn in V7 and check the global origin, what is displayed is 1) incorrect (for what we want), and 2) seems to always report the same triplet of values.
Is there anything needed to be done "differently" to handle the case of writing to 3D V7 files? Or - is there any way to specify the V7 output working units and global origin from the standard "File Save-As"?
Thanks,
Bruce