Generally not, unless you like to (although the templates are a bit boring)
Test one of the templates by installing WSS and creating a site
| Thanks again Jim...
| I suspected sharepoint might come into this discussion. I've only played
| with it a little. It's on my to do list to learn more about it. I see you
| wrote a book
| Question on Sharepoint.. I have my own W2003 servers, etc. I've played a
| little with sharepoint in the on-line tutorials, but if I were to set it up,
| I would much prefer it to run locally and keep my files in house. Is there
| a lot of customization that needs to be done to get it to perform well for
| me? I know it's an extremely generic question, so whatever you can say
| would be appreciated.
|
| Each person maintaining copies isn't my current solution. I have network
| shares, and directory rights pretty clean. It's just that there's only so
| much description you can build into file & folder names, and there are some
| people who are just frightened to death of that format vs. a nice web
| format.
|
| I have considered your suggestion of typing descriptions w/ hyperlinks. I'd
| just like pages to be self maintaining. There is already procedure that
| keeps the directories up to date with stardardized naming, certain people in
| charge of certain things, etc. As I try to move to using web interfaces,
| I'm trying to avoid what I see happen too often with that stuff, which is
| the creation of a new upkeep process and the possibility of two areas not in
| synch with each other.
|
| But I'm just getting into it, so we shall see.
| I really appreciate your feedback here!
|
| Tim
|
| | > Actually, the Microsoft solution for this type of requirement is Windows
| > SharePoint Services, a free-add-on component of Windows Server 2003.
| >
| > With Windows SharePoint Services, you create "Team Sites" that contain
| > announcements, event lists, contacts lists and so forth, plus as many
| > document libraries as you want. The document libraries "remember" and
| > display
| > much more information about each document than file and folder names can
| > convey, and when you click a document it opens immediately in Word,
| > PowerPoint, Excel, or whatever.
| >
| > In general, this is a lot cleaner than having each team member maintain
| > personal copies of each document.
| >
| > You can sign up for Windows SharePoint Services just as you would for any
| > other type of Web site. Of course, you need to find a hosting services
| > that
| > provides it.
| >
| > Otherwise, have you considered just making up a Web page with all the
| > descriptions and explanations you want, and then building hyperlinks to
| > the
| > corresponding files?
| >
| > Jim Buyens
| > Microsoft MVP
| >
http://www.interlacken.com
| > Author of:
| > *----------------------------------------------------
| > |\---------------------------------------------------
| > || Microsoft Windows SharePoint Services Inside Out
| > || Microsoft Office FrontPage 2003 Inside Out
| > ||---------------------------------------------------
| > || Web Database Development Step by Step .NET Edition
| > || Microsoft FrontPage Version 2002 Inside Out
| > || Faster Smarter Beginning Programming
| > || (All from Microsoft Press)
| > |/---------------------------------------------------
| > *----------------------------------------------------
| >
| >
| > "Tim" wrote:
| >
| >> Thanks Jim,
| >> Sounds to me like it'd be a nice little add in to FP. If I could just
| >> add
| >> in a ?control?, size it properly, and define the options (such as network
| >> location, perhaps types of files to display based on file extension or
| >> certain file properties, etc), and that was it, I could make use of that
| >> in
| >> numerous ways. Someone should build it. I'd pay some for it for sure.
| >>
| >> Really, what I'm looking for is to surround my directory structure with
| >> some
| >> intelligence for my internal staff. We have a lot of internal
| >> documentation, and there's only so much logic you can build into file and
| >> folder naming.
| >> I suspect there are other better ways, and that's probably why it hasn't
| >> been built.
| >> Tim
| >>
| >>
| >> | >> > I'm not sure if you could find something pre-written or not, but this
| >> > sort
| >> > of
| >> > thing is tricky. The problem is that the Web server can only transmit
| >> > one
| >> > file per request/response. As a result, you generally need an ActiveX
| >> > control
| >> > that can request and save the multiple files.
| >> >
| >> > The easiest approach, of course, is to just transmit a ZIP file and let
| >> > the
| >> > recipient unpack it.
| >> >
| >> > Jim Buyens
| >> > Microsoft MVP
| >> >
http://www.interlacken.com
| >> > Author of:
| >> > *----------------------------------------------------
| >> > |\---------------------------------------------------
| >> > || Microsoft Windows SharePoint Services Inside Out
| >> > || Microsoft Office FrontPage 2003 Inside Out
| >> > ||---------------------------------------------------
| >> > || Web Database Development Step by Step .NET Edition
| >> > || Microsoft FrontPage Version 2002 Inside Out
| >> > || Faster Smarter Beginning Programming
| >> > || (All from Microsoft Press)
| >> > |/---------------------------------------------------
| >> > *----------------------------------------------------
| >> >
| >> >
| >> >
| >> > "Tim" wrote:
| >> >
| >> >> I'd like a tool, preferably something I can place into a web page via
| >> >> FrontPage, that displays the files located in a pre-defined directory,
| >> >> and
| >> >> allow users to select multiple files and print or download them with
| >> >> one
| >> >> click (rather than having to interact with them one at a time). I
| >> >> picture
| >> >> this with check boxes, and control over sorting, and perhaps options
| >> >> to
| >> >> display some of the files attributes also.
| >> >>
| >> >> Certainly this is already built?
| >> >> Thanks for any direction!
| >> >>
| >> >> Tim
| >> >>
| >> >>
| >> >>
| >>
| >>
| >>
|
|
