I have a webpage that has about 118 pages. There are menus needed on about
90 of these pages.

Try this -

http://www.interlacken.com/winnt/tip...ow.aspx?tip=28



--
Murray
============

"JoeM" <(E-Mail Removed)> wrote in message
news:OLt6t%(E-Mail Removed)...
>I have a webpage that has about 118 pages. There are menus needed on about
>90 of these pages.
>

Looks good, but I may need a little more, 90 of the pages need to have the
same menus, I don't want to change the code in all of the pages, and not
all html files are located in the same locaton (but they are all are on the
same domain,server).

"Murray" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Try this -
>
> http://www.interlacken.com/winnt/tip...ow.aspx?tip=28
>
>
>
> --
> Murray
> ============
>
> "JoeM" <(E-Mail Removed)> wrote in message
> news:OLt6t%(E-Mail Removed)...
>>I have a webpage that has about 118 pages. There are menus needed on
>>about 90 of these pages.
>>
>
>

That's not a problem. Use a server-side or FP include for the menu. But
what do you mean by not at the same location? Do you mean that you are
linking cross-domain? That wouldn't be a problem either.

--
Murray
============

"JoeM" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Looks good, but I may need a little more, 90 of the pages need to have the
> same menus, I don't want to change the code in all of the pages, and not
> all html files are located in the same locaton (but they are all are on
> the same domain,server).
>
> "Murray" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Try this -
>>
>> http://www.interlacken.com/winnt/tip...ow.aspx?tip=28
>>
>>
>>
>> --
>> Murray
>> ============
>>
>> "JoeM" <(E-Mail Removed)> wrote in message
>> news:OLt6t%(E-Mail Removed)...
>>>I have a webpage that has about 118 pages. There are menus needed on
>>>about 90 of these pages.
>>>
>>
>>
>
>

Put the menus in a dynamic web template file (FP2003 only) or Server Side
Include (SSI which requires all files with the included page to have an
*.shtml extension) or Frontpage include component page (FP 2003 & earlier).

You will then have the one file with the menus but you still would have to
go through 90 files and include the file or attach the template to each
one - a lot of work nonetheless.

"JoeM" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Looks good, but I may need a little more, 90 of the pages need to have the
> same menus, I don't want to change the code in all of the pages, and not
> all html files are located in the same locaton (but they are all are on
> the same domain,server).
>
> "Murray" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Try this -
>>
>> http://www.interlacken.com/winnt/tip...ow.aspx?tip=28
>>
>>
>>
>> --
>> Murray
>> ============
>>
>> "JoeM" <(E-Mail Removed)> wrote in message
>> news:OLt6t%(E-Mail Removed)...
>>>I have a webpage that has about 118 pages. There are menus needed on
>>>about 90 of these pages.
>>>
>>
>>
>
>

All pages are in the same domain, example I have menus top
title,(FieldDeployment, OrderingShipping), like (File, Edit) are all folder
names, and inside these folders are the HTML documents that are linked to
the submenus of this menus.
A little confusing, and alot of work.

"Murray" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> That's not a problem. Use a server-side or FP include for the menu. But
> what do you mean by not at the same location? Do you mean that you are
> linking cross-domain? That wouldn't be a problem either.
>
> --
> Murray
> ============
>
> "JoeM" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Looks good, but I may need a little more, 90 of the pages need to have
>> the same menus, I don't want to change the code in all of the pages, and
>> not all html files are located in the same locaton (but they are all are
>> on the same domain,server).
>>
>> "Murray" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> Try this -
>>>
>>> http://www.interlacken.com/winnt/tip...ow.aspx?tip=28
>>>
>>>
>>>
>>> --
>>> Murray
>>> ============
>>>
>>> "JoeM" <(E-Mail Removed)> wrote in message
>>> news:OLt6t%(E-Mail Removed)...
>>>>I have a webpage that has about 118 pages. There are menus needed on
>>>>about 90 of these pages.
>>>>
>>>
>>>
>>
>>
>
>

Well about 90 files I need to change when I add or change a menu. If I
could have one place I can change this it would be great. I will try the
namic web template file since I am running Frontpage 2003. Thanks

"Andrew Murray" <(E-Mail Removed)> wrote in message
news:437a6006$0$9968$(E-Mail Removed)...
> Put the menus in a dynamic web template file (FP2003 only) or Server Side
> Include (SSI which requires all files with the included page to have an
> *.shtml extension) or Frontpage include component page (FP 2003 &
> earlier).
>
> You will then have the one file with the menus but you still would have to
> go through 90 files and include the file or attach the template to each
> one - a lot of work nonetheless.
>
> "JoeM" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Looks good, but I may need a little more, 90 of the pages need to have
>> the same menus, I don't want to change the code in all of the pages, and
>> not all html files are located in the same locaton (but they are all are
>> on the same domain,server).
>>
>> "Murray" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> Try this -
>>>
>>> http://www.interlacken.com/winnt/tip...ow.aspx?tip=28
>>>
>>>
>>>
>>> --
>>> Murray
>>> ============
>>>
>>> "JoeM" <(E-Mail Removed)> wrote in message
>>> news:OLt6t%(E-Mail Removed)...
>>>>I have a webpage that has about 118 pages. There are menus needed on
>>>>about 90 of these pages.
>>>>
>>>
>>>
>>
>>
>
>

That's a perfect justification for using an include. One file. One set of
changes. One page to publish. All pages reflect the changes.

--
Murray
============

"JoeM" <(E-Mail Removed)> wrote in message
news:uA$(E-Mail Removed)...
> All pages are in the same domain, example I have menus top
> title,(FieldDeployment, OrderingShipping), like (File, Edit) are all
> folder names, and inside these folders are the HTML documents that are
> linked to the submenus of this menus.
> A little confusing, and alot of work.
>
> "Murray" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> That's not a problem. Use a server-side or FP include for the menu. But
>> what do you mean by not at the same location? Do you mean that you are
>> linking cross-domain? That wouldn't be a problem either.
>>
>> --
>> Murray
>> ============
>>
>> "JoeM" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Looks good, but I may need a little more, 90 of the pages need to have
>>> the same menus, I don't want to change the code in all of the pages,
>>> and not all html files are located in the same locaton (but they are all
>>> are on the same domain,server).
>>>
>>> "Murray" <(E-Mail Removed)> wrote in message
>>> news:%(E-Mail Removed)...
>>>> Try this -
>>>>
>>>> http://www.interlacken.com/winnt/tip...ow.aspx?tip=28
>>>>
>>>>
>>>>
>>>> --
>>>> Murray
>>>> ============
>>>>
>>>> "JoeM" <(E-Mail Removed)> wrote in message
>>>> news:OLt6t%(E-Mail Removed)...
>>>>>I have a webpage that has about 118 pages. There are menus needed on
>>>>>about 90 of these pages.
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

FYI: FP will not manage the links, so the link would have to be absolute URLs to the pages.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

"Murray" <(E-Mail Removed)> wrote in message
news:OK6%(E-Mail Removed)...
> That's a perfect justification for using an include. One file. One set of changes. One page to
> publish. All pages reflect the changes.
>
> --
> Murray
> ============
>
> "JoeM" <(E-Mail Removed)> wrote in message news:uA$(E-Mail Removed)...
>> All pages are in the same domain, example I have menus top title,(FieldDeployment,
>> OrderingShipping), like (File, Edit) are all folder names, and inside these folders are the HTML
>> documents that are linked to the submenus of this menus.
>> A little confusing, and alot of work.
>>
>> "Murray" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> That's not a problem. Use a server-side or FP include for the menu. But what do you mean by
>>> not at the same location? Do you mean that you are linking cross-domain? That wouldn't be a
>>> problem either.
>>>
>>> --
>>> Murray
>>> ============
>>>
>>> "JoeM" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
>>>> Looks good, but I may need a little more, 90 of the pages need to have the same menus, I don't
>>>> want to change the code in all of the pages, and not all html files are located in the same
>>>> locaton (but they are all are on the same domain,server).
>>>>
>>>> "Murray" <(E-Mail Removed)> wrote in message
>>>> news:%(E-Mail Removed)...
>>>>> Try this -
>>>>>
>>>>> http://www.interlacken.com/winnt/tip...ow.aspx?tip=28
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Murray
>>>>> ============
>>>>>
>>>>> "JoeM" <(E-Mail Removed)> wrote in message news:OLt6t%(E-Mail Removed)...
>>>>>>I have a webpage that has about 118 pages. There are menus needed on about 90 of these pages.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Right - good clarification.

--
Murray
============

"Thomas A. Rowe" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> FYI: FP will not manage the links, so the link would have to be absolute
> URLs to the pages.
>
> --
> ==============================================
> Thomas A. Rowe (Microsoft MVP - FrontPage)
> ==============================================
> If you feel your current issue is a results of installing
> a Service Pack or security update, please contact
> Microsoft Product Support Services:
> http://support.microsoft.com
> If the problem can be shown to have been caused by a
> security update, then there is usually no charge for the call.
> ==============================================
>
> "Murray" <(E-Mail Removed)> wrote in message
> news:OK6%(E-Mail Removed)...
>> That's a perfect justification for using an include. One file. One set
>> of changes. One page to publish. All pages reflect the changes.
>>
>> --
>> Murray
>> ============
>>
>> "JoeM" <(E-Mail Removed)> wrote in message
>> news:uA$(E-Mail Removed)...
>>> All pages are in the same domain, example I have menus top
>>> title,(FieldDeployment, OrderingShipping), like (File, Edit) are all
>>> folder names, and inside these folders are the HTML documents that are
>>> linked to the submenus of this menus.
>>> A little confusing, and alot of work.
>>>
>>> "Murray" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> That's not a problem. Use a server-side or FP include for the menu.
>>>> But what do you mean by not at the same location? Do you mean that you
>>>> are linking cross-domain? That wouldn't be a problem either.
>>>>
>>>> --
>>>> Murray
>>>> ============
>>>>
>>>> "JoeM" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>> Looks good, but I may need a little more, 90 of the pages need to have
>>>>> the same menus, I don't want to change the code in all of the pages,
>>>>> and not all html files are located in the same locaton (but they are
>>>>> all are on the same domain,server).
>>>>>
>>>>> "Murray" <(E-Mail Removed)> wrote in message
>>>>> news:%(E-Mail Removed)...
>>>>>> Try this -
>>>>>>
>>>>>> http://www.interlacken.com/winnt/tip...ow.aspx?tip=28
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Murray
>>>>>> ============
>>>>>>
>>>>>> "JoeM" <(E-Mail Removed)> wrote in message
>>>>>> news:OLt6t%(E-Mail Removed)...
>>>>>>>I have a webpage that has about 118 pages. There are menus needed on
>>>>>>>about 90 of these pages.
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>