Hi
I want to achive the following.
I have 10 InfoPath documents wich all represents a step in a Wizard like
visualization. The customer want a menu to the left consisting of 10 links
to each step (text links).
I could create a InfoPath 2007 document with 10 views and shift between
these...if i could make a [text button] to trigger an View change event.
This control does however not exist and regualr buttons is not an option :(
No my other solution. Now i have tried to create custom aspx page with a
XmlFormView control hosting one of these 10 steps. My idea was to load the
view with a particualar step (filling when user press menu item on the
regular aspx form). This works. great.
And now the actual quiestion. I NEED to be able to save the document when
the user presses and new menu link (outside the XmlFormView). I thought i
would be possible to do something like
void myMenuEventHandlerStep2(...)
{
XmlformView1.Save(); // No go
XmlformView1.Xsnlocation = ("link to the next step");
}
But there is no Save() method on the XmlFormView1. How can i achive this. I
can only find information about triggering event ON the form to the host.
Thanks in regards
Anders J
Anders J - 07 Mar 2007 13:10 GMT
(the Aurthor of this thread)
I found that i can have a mothod like
XmlFormView1.XmlForm.Save();
That looked promising..but..I get a...
:: The method or operation is not implemented.
Still need suggestions....!
Regards
Anders
> I want to achive the following.
>
[quoted text clipped - 28 lines]
> Thanks in regards
> Anders J
Wozza - 08 Mar 2007 12:13 GMT
I don't understand why a regular button is not an option. If you remove the
formatting (background colour) and border, you can make the button look like
a "text button".
Just right-click the button and click "Borders and Shading" ...
I have done this by placing a single button, in a repeating table. By maknig
the table bound to a list of views (hard coded in (perhaps) a second
datasource ... this works a treat???
> Hi
>
[quoted text clipped - 30 lines]
> Thanks in regards
> Anders J
Anders J - 08 Mar 2007 13:55 GMT
> I don't understand why a regular button is not an option. If you remove
> the formatting (background colour) and border, you can make the button
[quoted text clipped - 4 lines]
> maknig the table bound to a list of views (hard coded in (perhaps) a
> second datasource ... this works a treat???
Jeee. You are right. That is a perfect solution! Don't know how I could miss
that "button styling" approach. Thanks a mill.
Regards
Anders