Thank you, didn't know about it :D

What do dyslexia and cross-eyed have in common They both look at the world a little differently :-\ Steve _________________ I C(++) therefore I am

Lucian-aSterX wrote: i should use WPF Indeed. :-D [Forum Guidelines]

yEd[^] is pretty good.

Generally I do not use gotos in c# but there is one exception with regards to switch (cases) where you want to process multiple cases. For example, I have a data driven website where certain css classes are listed in data and applied to a user control in order. They are all optional but want to process each one specified in a specific way, so I created something like: char sepChar = '|'; string[] array = dataString.Split(sepChar); switch (array.length) { case 3: dosomeassign(array[2], element5); goto 2; case 2: dosomeotherassign(array[1], element4); goto 1; case 1: dosomeassign(array[0], element2); break; } WarePhreak Programmers are tools to convert caffiene to code.

Electron Shepherd wrote: all you needed to do was double up any single quotes in each parameter How about for NULL (no quotes, though that wouldn't be much use in the specific case of an IN operator)? And for date times ("3/6/2010" is March 6th or June 3rd, and that doesn't even take into account millisecond precision)? And for numbers (no quoting necessary)? And when C# uses scientific notation to represent numbers but SQL Server does not ("100000000.0" vs "1.0E8")? Or when a different culture processes certain data types (e.g., date times) differently? Not so simple after all, now is it? And I think it wasn't very hard to create a list of strings in the format "@param0, @param1, ..., @paramN". As far as bulk inserts... that is quite efficient. But different strokes for different folks. [Forum Guidelines]

...and forever be someone's bitch. -- Kein Mitleid Für Die Mehrheit

You can do it your own way, or try using the slipstreams of others. If you do not use a SCM system then it might be hard to learn from others. If you do have a SCM you can learn from someone that knows how SCM can help your software through transition stages e.g. learn from those that (prob.) produce the best SCM (http://www.perforce.com/perforce/papers/bestpractices.html[^]) and/or those that communicate SCM patterns (http://www.cmcrossroads.com/bradapp/acme/branching/branch-structs.html[^] and http://www.scmpatterns.com/book/pattern-summary.html[^]). Another thing that could come in handy, is the ability to talk about SCM experiences and opinions; think job interviews or future partners (the business kind - others might fall asleep ;) ).