I seem to have a problem with @Command( [SwitchForm]; “NewForm” ) / @Command( [ViewSwitchForm]; “NewForm” ). If there is no form formula in the view from which the document is opened, I can use a button with the @Command in it to swap the form fine. However, as soon as a form formula is in effect on the view it seems to be impossible to switch the form.
Is this a known “feature”? Has anyone else had this, or am I just doing something stoopid?
Subject: @Command( [SwitchForm] ) and form formulas
A view form formula wins - if you say ‘use this form’, end of story. The idea behind form formulas is that there something SO important about what form is used in this view, that it MUST be forced to be used. If you need to allow users to switch forms, drop the form formula.
Subject: RE: @Command( [SwitchForm] ) and form formulas
The users can set which form they would like to use as a preference, as there are two designs in use - the “default” one, and a different one. If they choose the default one, no problem, the switch form works because the form formula works out to “Form”. If they choose the different one, the form formula kicks in in the view to open it in the different form. That they can’t then change it back to the default form should they want to seems a bit annoying, considering it works the other way.
Perhaps I will try a SwitchForm in the postopen of the form or something…
Subject: RE: *Can you show us the form formula, as I don’t gt what you want to accomplish?
Hi Ben,
Here’s the form formula. Basically, people copy project related emails into a database so that they all have access to them. Originally there was only one form design to show these emails, but some people wanted them laid out differently (more like memo’s in their mail file). They also (rightly) said that it’s an arse-ache to have to swap form every time they wanted to look at one, so could I make it a preference… (FromEmail is a field on the forms that is set if the document has been pulled in from their email).