HELP - Compose Document Stuffed

Hi All,

I have a database which is in development and no matter what form I use in the @Command([Compose]) it always seems to use the same form??? I thought I might have some corruption so I created a template from the database, restored the original and then applied the template…same result.

Any ideas??

Thanks,

Terry

Subject: HELP - Compose Document Stuffed

Silly question, but I am assuming that you are using the command:@Command([Compose]; “Name of Form”)

Subject: I kid you not…

Yes I am using the @command([Compose];‘Name of form’). I have isolated the problem down to a Form Select formula in a view. If I remove the form select formula from this view ie

@If(@ClientType = “Notes”; “frmCorpsInfo”;“frmWebCorpsInfo”)

then the bizarre behaviour I described does not occur. The form which is used in any @command(compose) formula is always frmCorpsInfo. Does not matter if I create the form using an action button or via the Create document menu.

This one is a BEAUTY!!! Any ideas gang??

Thanks

Subject: Operating as designed

Like it or not, a form formula takes precedence. Of course, you can override it simply by changing the form formula to

@If(@IsNewDocument; Form; @ClientType = “Notes”; “frmCorpsInfo”;“frmWebCorpsInfo”)

and making sure there is a Form field on the form which computes to the form name. (Actually, I am not sure you need to add the field, but I think you do.)

Subject: RE: Operating as designed

Thanks that worked…I thought the form formula was only used in selecting which form to use for displaying…but the documentation does infact say ‘form formula determines which forms are used for composing and displaying documents’…seems a bit strange to me…but I’ll run with the solution.

Cheers,

Terry

ps…No you dont have to add a form field to the form.