Merging methodology for Forms / Reports

raven44

Hi,

Is there some sort of methodology, or formula, prority that can be used when merging Forms or Reports?

Ie. when I merge these objects - I often have a button out of place, or fields over lapping one another.

Whats the best method of choosing which code is to be placed into the merged object.

Thanks.

ara3n

List form are easy to merge,
The issue is the card and order forms. Those I usually text compare them to find the differences, and make the same modification manually, by copying and pasting the controls from one form to another.

kriki

ara3n wrote:

Those I usually text compare them to find the differences, and make the same modification manually, by copying and pasting the controls from one form to another.

To copy/paste the controls from one form to another, both versions need the same client version.
E.g. you want to merge customer changes in 3.10-objects to 4.00SP3, first put also the customer changes in 3.10-objects on a 400SP3-client.

ara3n

yep that's what I do the first thing when I upgrade.

kriki

ara3n wrote:

yep that's what I do the first thing when I upgrade.

Me too, but maybe others don't think about it.

ara3n

I see. :P

DenSter

I merge forms with Beyond Compare. After you've done a few you start recognizing where things go and what things mean, and you'll know when you need to check for alignment.

I usually just make sure that controls are on the right tab in BC, and then move them away from eachother in the form designer. This is for me by far the fastest way to do it, MUCH faster than making the changes manually.

raven44

thanks for your answers everyone.
seems I'm on the right track, just thought I may be doing something the long way as I often would need to do some sort of manual manipulation with the merged objects.

David_Cox

I always do a manual visual merge for forms and reports, where the version has changed, as there may have been new fields controls or menu items added for the new version, which could conflict with what you have done.

A good example would be PO Authorisation having done several different Customer specific versions, when it comes to moving up to version 5 where it has been added as standard, and the Customer may want to keep or drop thier version, the merge would not work very well here.

And "What you see is what you get" :shock: 8)