Okay - so we open up our infopath form, modify the XSL files so tha
we can make the text boxes sunk to match the combo boxes (lovely fo
MS not to have that option in the designer). But it work
intermittently - I open a form and the boxes haven't changed, yet th
XSL file for the view does specify "style='border-style:inset'"
Anyone have any clue what causes this, or a way to get around it?
We've specified both inline and general styles. They work for som
time, and then apparently InfoPath just decides to ignore them.
It's freaking ridiculous - we've lost about 2 man days because of thi
and other MS caching 'features'
Brian Teutsch [MSFT] - 18 Mar 2005 20:48 GMT
Touch (open & save) the manifest.xsf file. This will cause InfoPath to
reload the entire form. Sorry you are annoyed by the caching, it is a very
desireable feature when the forms are living on a web server, when checking
each file or downloading every single time is costly.
Brian
> Okay - so we open up our infopath form, modify the XSL files so that
> we can make the text boxes sunk to match the combo boxes (lovely for
[quoted text clipped - 8 lines]
> It's freaking ridiculous - we've lost about 2 man days because of this
> and other MS caching 'features'.
mathieson_sterling - 23 Mar 2005 08:47 GMT
> Brian Teutsch [MSFT]wrote
"]Touch (open & save) the manifest.xsf file. This will caus
InfoPath to
> reload the entire form. Sorry you are annoyed by the caching, it i
a very
> desireable feature when the forms are living on a web server, whe
checking
> each file or downloading every single time is costly
You're quite right - and now that I've calmed down I can agree wit
you. It's just very frustrating when you're first working wit
InfoPath, as you don't know where the caching is occuring
Thanks for the answer