P
Parky
Is there an alternative Microsoft produce to replace MS Binder?
Not a big fan of adobe - would prefer to use a Microsoft product.
Not a big fan of adobe - would prefer to use a Microsoft product.
B
Bob I
No.
J
JoAnn Paules
Have you looked at using .xps files? I know very little about them so I'm
not sure how different formats could be combined. (Apparently they can.)
not sure how different formats could be combined. (Apparently they can.)
B
Bob Buckland ?:-\)
Hi JoAnn,
The internal structure of Micrsoft XPS (XML Paper Specification) 'documents' are similar to the structure Office 2007 core app
documents.
They are, internally, a collection of XML managed document parts, hosted in a .ZIP package with a different filetype extension, in
this case .XPS.
As with the Office 2007 filetypes you can manipulate the contents of the zip containers independently of the creating app, but it's
more of a developer thing than an end user one
For practical purposes, MS XPS Writer (available in Office 2007 as an addin for 'Save As=>XPS', creates files that for the end user
are along the same line as PDF files (basically static results)
MS Office Binder was an Office file shell that sort of combined the capabilities of MS Windows Briefase, to allow transport of a
set of 'project'/related files, but allowed folks with Office to edit, individually the files in the Binder and then to print the
binder contents with a single set of page headers/footers. A drawback of the Binder was that the files in the binder couldn't
'talk' (link) content to each other easily.
About the closest MS offers in functionality would be Sharepoint or you can do some of the same things, for printing through OneNote
pages.
===================
Have you looked at using .xps files? I know very little about them so I'm
not sure how different formats could be combined. (Apparently they can.)
--
JoAnn Paules >>
--
Bob Buckland ?
MS Office System Products MVP
*Courtesy is not expensive and can pay big dividends*
The internal structure of Micrsoft XPS (XML Paper Specification) 'documents' are similar to the structure Office 2007 core app
documents.
They are, internally, a collection of XML managed document parts, hosted in a .ZIP package with a different filetype extension, in
this case .XPS.
As with the Office 2007 filetypes you can manipulate the contents of the zip containers independently of the creating app, but it's
more of a developer thing than an end user one
For practical purposes, MS XPS Writer (available in Office 2007 as an addin for 'Save As=>XPS', creates files that for the end user
are along the same line as PDF files (basically static results)
MS Office Binder was an Office file shell that sort of combined the capabilities of MS Windows Briefase, to allow transport of a
set of 'project'/related files, but allowed folks with Office to edit, individually the files in the Binder and then to print the
binder contents with a single set of page headers/footers. A drawback of the Binder was that the files in the binder couldn't
'talk' (link) content to each other easily.
About the closest MS offers in functionality would be Sharepoint or you can do some of the same things, for printing through OneNote
pages.
===================
Have you looked at using .xps files? I know very little about them so I'm
not sure how different formats could be combined. (Apparently they can.)
--
JoAnn Paules >>
--
Bob Buckland ?
MS Office System Products MVP
*Courtesy is not expensive and can pay big dividends*
J
JoAnn Paules
Thank you. I'd never used Binder and only once used an .xps file. It did
what I needed and that's all I cared about. ;-)
what I needed and that's all I cared about. ;-)