What are the differences/advantages of one over the other?

I have a Win2000 server running FPSE v. 5.0.2.4330, but MS shows latest
version as 5.0.2.2623.

can only assume that I'm running SPSE.  Why should/shouldn't I be?

>Kevin

[ Post a follow-up to this message ]

Kevin,
That doesn't necessarily mean you're running the SharePoint Server
Extensions. Some of the fp server extensions are actually patched by the Win
2000 Service Packs, so the versions may show differently than what you'll
see on the web site.  Basically though, a SharePoint will also install and
require a databaase to store it's data. SharePoint essentially adds document
library sharing abilities, threaded discussions, and other items that may be
needed in an intranet setting.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage

"KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message
news:06365F64-B6D3-4B9A-AD81-290A6520E78A@microsoft.com...[vbcol=seagreen]
> What are the differences/advantages of one over the other?
>
> I have a Win2000 server running FPSE v. 5.0.2.4330, but MS shows latest
> version as 5.0.2.2623.
>
> can only assume that I'm running SPSE.  Why should/shouldn't I be?
> 

[ Post a follow-up to this message ]

Thanks for the reply Mark.

That said, how would/could users be effected when publishing from a testing
site running IIS4/FPSE 5.0.2.2623 to a staging site running IIS5/FPSE
5.0.2.4330?

Could these discrepancies be causing anomolies in the FP2002 client such as
items appearing as PUBLISH with FileSize=0KB, and users (Advanced Authors)
not being able to set files to DO NOT PUBLISH?

Apologies if this is not the correct forum to be discussing this...

Kevin

"Mark Fitzpatrick" wrote:

> Kevin,
>         That doesn't necessarily mean you're running the SharePoint Server
> Extensions. Some of the fp server extensions are actually patched by the W
in
> 2000 Service Packs, so the versions may show differently than what you'll
> see on the web site.  Basically though, a SharePoint will also install and
> require a databaase to store it's data. SharePoint essentially adds docume
nt
> library sharing abilities, threaded discussions, and other items that may 
be
> needed in an intranet setting.
>
>         Hope this helps,
>         Mark Fitzpatrick
>         Microsoft MVP - FrontPage
>
> "KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message
> news:06365F64-B6D3-4B9A-AD81-290A6520E78A@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Probably not. Most of the differences in the extensions are simply security
patches and performance tweaks and not really functionality alterations.

One of the things to check with the Do not publish feature is that they are
not trying to set it on a directory. Directories can't have this feature set
for some reason but the files inside a directory can. Some users don't make
the connection though and become frustrated and think it's a bug. Also ask
users if they have applied all the service packs to FP 2002 through the
office.microsoft.com web site. Sometimes these discrepancies are caused in
an unpatched version.

Hope this helps
Mark Fitzpatrick
Microsoft MVP - FrontPage

"KMcDermott" <KMcDermott@discussions.microsoft.com> wrote in message
news:959F37A4-F9FD-44AE-9E35-62D7F94220D2@microsoft.com...[vbcol=seagreen]
> Thanks for the reply Mark.
>
> That said, how would/could users be effected when publishing from a
> testing
> site running IIS4/FPSE 5.0.2.2623 to a staging site running IIS5/FPSE
> 5.0.2.4330?
>
> Could these discrepancies be causing anomolies in the FP2002 client such
> as
> items appearing as PUBLISH with FileSize=0KB, and users (Advanced Authors)
> not being able to set files to DO NOT PUBLISH?
>
> Apologies if this is not the correct forum to be discussing this...
>
> Kevin
>
> "Mark Fitzpatrick" wrote:
> 

[ Post a follow-up to this message ]