"Martin Eyles" <> wrote in message
news:...
> "Marina Levit [MVP]" <> wrote in message
> news:%23w$...
>> The typical way this is handled, is to have the form on the page, and the
>> user control, or web control, is simply placed on the page and becomes
>> part of its form.
>
> OK, will try this, and will hopefully work. Thanks.
Works beautifully. I now have a form with id="Form1" on all pages.
Once again, thanks!
Martin
>> "Martin Eyles" <> wrote in message
>> news:...
>>> OK, I have taken a look at the system. The way it works is that there is
>>> a page, and 1 custom control. The main page doesn't have a form, but the
>>> control does. The name of the form on my development server is
>>> __aspnetForm, and the name of the form on the server I deploy to is of
>>> the form controlInstanceName_Form1.
>>>
>>> "Marina Levit [MVP]" <> wrote in message
>>> news:...
>>>> Sorry, I've never heard of something like that happening. I don't know
>>>> why the server would be generating a different name for the form based
>>>> on the PC the request came from, unless you have some code there to
>>>> change this.
>>>>
>>>> I would put together a very simple page, and see if the problem still
>>>> happens. If not, I would see what this page is doing that would cause
>>>> this type of effect.
>>>>
>>>> "Martin Eyles" <> wrote in message
>>>> news:...
>>>>>
>>>>> This is however was masking another problem, which I have put in a
>>>>> reply to the original message. any help there would also be
>>>>> appreciated.