In very brief testing, it appears that the form fields are skipped over when there are CCs in the file. I've seen mvps and admins on this and other forums vaguely advise against intermingling CCs and legacy fields so that may be the reason that advise is provided. I have not yet seen other problems when this happens but if it can be avoided I would say you should stick with one or the other.

The method the Client Mgmt DB uses to populate the bookmarks is an unknown factor so if you can't manipulate it and it is critical to the document usage then I would probably stay exclusively with legacy fields. Or else you lose the 'tab into fields' functionality.

You could conceivably use bookmarks inside a rich text CC but the bookmark would likely be destroyed if someone tabs into the CC and types. Conversely, putting the bookmark outside the CC would remove the CC when the DB updates the bookmark value. Either way there is a drawback that you should avoid if the DB is updating content as well as allowing users to tab across fields and possibly retype content.

__________________
Andrew Lockton
Chrysalis Design, Melbourne Australia