-
You can always use a preserve code block (do a search for info about that) and write the table code yourself. Then you can do things like you are talking about.
The downside is that once you are in a preserve code block, you cannot modify the table in the designer--you have to do it by hand in the .xsl file.
-
You can go into the properties for the text box and set it to expand as necessary. If you already have that, try placing the text box inside a scrolling region.
-
If you want to use a drop-down list as a master control, then you do not want to use the Master/Detail control. Instead you just want to filter your section or table based on the selection in your drop-down list.
-
InfoPath performance has been covered numerous times. Basically it sounds like you would run into a couple of bottle necks:
1. The amount of controls in a single view. This is alleviated by creating multiple smaller views.
2. The amount of data loaded at one time. This can be alleviated by pulling in only what you need for the particular view, ...
-
For InfoPath 2003, you need to purchase additional software to make your forms work in the browser. This capability was added to InfoPath 2007.
Check outhttp://www.qdabra.com/proddetail.asp?prod=QFormsViewer
Also check outhttp://www.infopathdev.com/resources/internet/default.aspx?s=Web%20Form%20Conversion
-
First your form needs to support merging. This is in the form options.
Next the different forms you want to import either need to be of the same schema, or you need to write some custom import XSLs for each schema (too much to get into here... but Microsoft has some tutorials on this).
Once you've got the above in place, you either import one ...
-
There have been issues reported in regards to IE7 and InfoPath images. I don't know whether this is the case for your particular scenario.
Since you mention that it happens during print preview, check your settings to ensure that background images and colors are set to print. This option is turned off by default.
-
You shouldn't need a custom XSLT to do this. There is supposed to be some way to specify for the SharePoint field how many decimal places to show. I've not done it myself, but was recently involved in a thread where the other user did it.
-
To answer your two questions at the bottom of your posting:
1. Combo boxes can't take borders. This is not an InfoPath limitation, but an Internet Explorer limitation that carries over to InfoPath because InfoPath uses Internet Explorer to render its views.
2. Place a default value formula on the field that converts the typed in content to ...
-
Importing a Word document is a much better experience in InfoPath 2007. But since you are using 2003, you might find it easiest (and cleanest) to simply start building your form from scratch.