Managing editboxes and labels...

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I am working on a project which requires converting an existing VB
application into web based application.The web application consists
following ,

1. Tab control on the left side containing 4 tabs and each tab
consisting of about 50 cotrols each.

2. Right side consists of about 50-60 controls.

The controls are mainly editboxes and labels.

What is the best way to design the page ? The application already has
a frameset with left and right frames.All the above controls will sit
in the right frame.Any suggestions on designing this will be very
helpful.

Thanks,

.

Relevant Pages

  • Re: IDE bugs
    ... 300 controls in 20 tab pages sounds like overkill - in fact, ... building that tab control at runtime with code instead of design time ... > last week everything was working fine until out of the blue the ide ...
    (microsoft.public.vsnet.ide)
  • Re: ModifiedFormPages -> Enabled = False
    ... Either design the form with all the controls on that tab disabled or hide the tab completely and show it only when needed, or write code to disable the controls one at a time. ... In Outlook 2000 or earlier using code to hide and show a tab will one-off a form, ...
    (microsoft.public.office.developer.outlook.forms)
  • Re: 3 final issues.. how to solve ?
    ... If the tab key does not work as expected, ... Select one of the controls where the tab does not ... Open the form in design view. ... > to the next entry field. ...
    (microsoft.public.access.forms)
  • Re: Form Questions
    ... > 1) While in design view, I have a form that has a lot of information ... even a height of 22 inches is cumbersome to work with. ... on each page of the tab control, ... there's a trick to moving existing controls from the body ...
    (microsoft.public.access.forms)
  • Re: 3 final issues.. how to solve ?
    ... >If the tab key does not work as expected, ... Select one of the controls ... >Open the form in design view. ... >> to the next entry field. ...
    (microsoft.public.access.forms)