Када радите са тастерима на обрасцу, we often add rules. You access the rules editor from the properties of the button.

Када кликнете око брзо, it’s easy to accidentally click on "Edit Form Code" instead of "Rules …".

Први пут сам ово урадио, I canceled out of the code editor. Међутим, када сам покушао да објаве начин касније мало, it required that I publish as an "Administrator-approved form template (напредан)". I didn’t actually do any programming and I absolutely didn’t want to go through an unnecessary approval process. I was in a bit of panic at the time due to time constraints. To get past it, I simply restored a previous backup and continued. I had recently seen some blog posts about people going into the form’s XML to tweak things and I was afraid I would have to do something similar.

Данас, I did it again. Овај пут, Имао сам мало више времена на рукама и открили да лако можете да опозовете.

Иди на:

Алати -> Форма Оптионс -> Програмирање: "Remove Code"

То не би много лакше него да.

</крај>

ИнфоПатх образац Сервер Еррор поруке доводи у заблуду.

У развоју ИнфоПатх обрасцу, Ја бих га поставите на МОСС сервер и приступ образац. Формулар ће почети да се учита, а затим створити погрешну поруку о грешци указујући ми на Виндовс евиденцији догађаја за детаље. Заправо, no message was written to the windows event log. Rather, the message was sent to the MOSS ascii diagnostic log. You can track that down via central services administration.

You need to be quick on your feet. MOSS likes to write to the log file, frequently and verbosely. This can be trimmed but the default log writing behavior is "everything as quickly as possible".