A few weeks ago I found myself needing to create a Windows Form application that would allow the user to enter details for an operation over several steps and then commit the operation in the final step. Essentially, I wanted to create a ‘wizard’.

Many is the time that I have had a list, perhaps created in the front-end of a program that, was pushed through to the database and then needed to be iterated through. Essentially I wanted a simple way to do what in JScript or CSharp is a String.Split(’,'), returning an array of strings.

I first created this post as a question because after several hours of searching online I couldn’t find a straightforward solution to a problem I had. Here briefly is a description of what I was trying to do and the problem I had.

This isn’t the first time I’ve had to deal with orphaned users in SQL Server, and probably won’t be the last but today I found myself investigating why it happens and how to resolve the issue it causes. I guess before I start on that I should explain what an orphaned user is.

This article was inspired by an idea in a blog entry by Omar Al Zabir. I found when implementing the idea that it needed some fleshing out and clarification, and so I decided to write my own version.