StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10598954
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-05-15T10:38:03.427
FavoriteCount
0
LastActivityDate
2012-05-15T11:41:35.303
LastEditDate
2012-05-15T11:41:35.303
LastEditorUserId
1129682
OwnerUserId
1129682
ParentId
10456106
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I know posts like that can cost me, but, seriously, back off a step and reconsider what you are trying to accomplish. A user who can view and print your report using Word also has IE available and most likely has easy access to Chrome. So my guess is Word is not just for viewing and printing, but especially for editing. I followed your example and my (unmodified in every aspect) IE9 will not print page breaks inserted using Word 2010 and the resulting HTML-document has hardly any resemblance with the initial one, especially the DIVs are gone, so assuming the document still prints the same after Word has had its say is almost carelessly optimistic. This entire idea seems broken: <ul> <li>writing HTML your way seems pointless given what Word does with it</li> <li>even a recent IE can't handle your simple example with page breaks inserted using Word</li> <li>when saving Word created a language setting specific directory and three new files, which spawn a ridiculous big host of necessary tests for any product</li> <li>a lot of user knowledge (spawning directories, how to save correctly, how to copy the entire document correctly) seems required to make this work even within a static Microsoft eco-system</li> <li>it appears user defined settings can easily break any solution employing HTML</li> </ul> I'd suggest initially writing your report as a Word document. Even though zipped, Word documents are still markup like HTML so if you already can generate HTML, you can generate Word with little extra effort. As you can get Word viewers for virtually every x86 or ARM based device that seems a more reasonable direction than exploring in a direction where even the simple examples fail.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCreating Page Breaks for Chrome, Explorer and word in html
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USuser1129682
UserOwnerUserId
1. USuser1129682
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.