Object reference not set to an instance of an object

Most likely, c is not null, because the constructor should create this instance, but nothing is selected. Then frmobject.comboBox1.SelectedItems returns null, which is fine. But then you try to dereference this null object by calling its instance method ToString(); and this is what throws this exception. Apparently, you should not do such things before you set some selection.

But you cannot ask such questions every time similar things happen. It's very important to cope with such situations by yourself. Not to worry. This is one of the very easiest cases to detect and fix. It simply means that some member/variable of some reference type is dereferences by using and of its instance (non-static) members, which requires this member/variable to be non-null, but in fact it appears to be null. Simply execute it under debugger, it will stop the execution where the exception is thrown. Put a break point on that line, restart the application and come to this point again. Evaluate all references involved in next line and see which one is null while it needs to be not null. After you figure this out, fix the code: either make sure the member/variable is properly initialized to a non-null reference, or check it for null and, in case of null, do something else.

Please see also: want to display next record on button click. but got an error in if condition of next record function "object reference not set to an instance of an object".

Sometimes, you cannot do it under debugger, by one or another reason. One really nasty case is when the problem is only manifested if software is built when debug information is not available. In this case, you have to use the harder way. First, you need to make sure that you never block propagation of exceptions by handling them silently (this is a crime of developers against themselves, yet very usual). The you need to catch absolutely all exceptions on the very top stack frame of each thread. You can do it if you handle the exceptions of the type System.Exception. In the handler, you need to log all the exception information, especially the System.Exception.StackTrace:
http://msdn.microsoft.com/en-us/library/system.exception.aspx,
http://msdn.microsoft.com/en-us/library/system.exception.stacktrace.aspx.

The stack trace is just a string showing the full path of exception propagation from the throw statement to the handler. By reading it, you can always find ends. For logging, it's the best (in most cases) to use the class System.Diagnostics.EventLog:
http://msdn.microsoft.com/en-us/library/system.diagnostics.eventlog.aspx.

By the way, never ever use auto-generated names such as comboBox1. They violate (good) Microsoft naming conventions (by obvious reasons). You are supposed to rename everything to give members semantically sensible names; only then you can develop maintainable code which is not pain to look at. After all, you are given the refactoring engine in Visual Studio.

Good luck,

—SA

The answer is probably simple. I do not know completely how you build your solution, but SelectedItem can be null if nothing selected in ComboBox.

Try something like this, probably it will help:

frmInvoice frmobject = new frmInvoice();

string str;

if (frmobject.comboBox1.SelectedItem != null)
    str = frmobject.comboBox1.SelectedItem.ToString();
else
    str = "None selected";