Quote:I don't know where's the faulty part
Your code do not behave the way you expect, or you don't understand why !
There is an almost universal solution: Run your code on debugger step by step, inspect variables.
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't know what your code is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
To see what your code is doing: Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide
Basic Debugging with Visual Studio 2010 - YouTube
The debugger is here to only show you what your code is doing and your task is to compare with what it should do.
Quote:I wonder if you call this an answer or a solution.. I also wonder if you read the post, tags or at least the title..
I read memes about posting a code on Codeproject as a beginner and how some people eat him a live!! Now I understand.
I started my post about being a extremely beginner which means a did my best.
I hope that I got a useful hint or help instead of blaming or self flagellation..
In practice, we have no way to reproduce your problem as it depend on your configuration and probably on your database.
The debugger will help you to spot the position of crash and get context. And if no crash, it will show you exactly what is doing your code.