Heiko

Hello there. I am having problems with the SelectNextControl Method, which I use to handle TAB-bing. Although the code is identical for both directions, the forwards direction seems to work (always) while the backward direction hangs - occasionally. Some "compound user controls" will not be left, although TAB-bing could continue on their parent. Has anybody else experienced this ?

Microsoft is a very professional company. I would not categorize this as a personal blog but rather see it as yet another marketing channel.

I don't see any use in giving the dynamic controls specific names. If you need to address them directly by their name this somehow implies that you knew of their existance even before you created them. OK. Before this gets too philosophical: You can access your dyna-controls through the controls collection of their container. Additionally you may want to keep them in a collection or specialized collection to associate names to controls.

The "optional" part will probably be part of the package in any way. (Well, at least *I* wouldn't want to build to different sets for shipping.) So I see two options: Future users have to contact you to enable the optional part. --> You can keep track of the installs. You negotiate an all inclusive package.

Don't forget to think about the poor guy who will have to do support and maintenance for your program, once that it's finished. To me, the idea of dynamic enumerations seems to be more on the "research" side than on the "practical" side.

Have you evaluated the DockingStyle property ? Controls need not necessarily reside on a panel. You can also place them directly on the form. I would not recommend this. Not at all. Because you will either get your sizing / docking scrambled when you remove / add or you have to work with fixed locations which is crap too. Another solution might be to add a public method .AddControl (location as myApp.myLocationEnumeration, control as control) to the main form.

I was getting syntax errors when I omitted the blanks between the concatenators. Did not work: theSQL = "SELECT name FROM member where name = '"&p_name&"'" Did work: theSQL = "SELECT name FROM member where name = '" & p_name & "'"

I would not expect a Univ professor to teach best practises or give recommendations on coding level. I would expect hin to help me understand the underlying basic principles, maybe some patterns, too.

Whoa. I'm going to get a fence because my son may has started *walking*. :-)

So will this happen to all rows with rowstate "added" ?

Thanks, but that doesn't help too much. Imagine we have a control names "ctlInvolvedPersons". This control is being used on various other controls, e.g. "ctlChirurgy", "ctlTransport", "ctlContact". ctlInvolvedPersons may be at the very top of ctlTransport, somewhere in the middle at ctlChirurgy and at the bottom of ctlContact.

Hi there, we are having a hard time with <TAB>bing in our application. We are developing with VB.NET 2002, Framework 1.0. We did set the tab-sequence with corresponding feature the IDE. First - when the user clicks into a textbox, say it's the fifth control on the current form - and then presses <TAB>, tabbing will start at the "beginning" of the form. I would rather expect it to continue at the current cursor position. Weird. Second - in many cases we place user defined complex controls on the form at runtime. Apparently, they are not correctly recognized because the cursor jumps in a really awkward way. Weird. Our users, however, demand an application that is 100% "keyboard usable". Now we're in trouble. Has anyone else experienced something the like ? Any embarrassing basic stuff that we simpy overlooked ? Any help / hint is appreciated. Thanks. Heiko

http://www.xtremedotnettalk.com/showthread.php?t=82947

Uh. I didn't have to tackle that problem. Can you add the event handlers by code ? Public Class malFunctionsTextBox Inherits TextBox Private _mF as new mFHelper Private Sub New() Mybase.New AddHandler me.OnClick, AddressOf _mF.Click End Sub End Class

You could try to place the controls on panels. One panel for each control. Each panel with dock style top. When you remove a panel (or set it invisible or it's height to zero), the others should move up.