lonewolff

This is more for a network client utility (rather than a game). So, if a user puts in dodgy stats, then they are essentially 'cheating' themselves.

Their dodgy stats wont have any effect on other users or the other users 'experience' within the app.

So, this is probably the option I will take (at this stage) to reduce development time. If the app becomes popular (dependent on completion of-course), I might up the security then.

Thanks Hodgman

What about if the client was supplied with credentials that limit them to the use of their own area of database?

Would this suffice?

Hi Cryptiik

There are some tutorials I wrote over on www.win32developer.com that should get you started.   

They will get you doing what you are after pretty easily. Basically you can cut & paste and you will be up and running.

But, once you are a little more confident you will have to handle error correction and packet framing etc, for better reliability and so on.

I am python-less and it works here 

My pet peeve is not making it clear that variables are member variables, but that's more of a C++ism I guess than a C# one. The problem is someone reading your code will have a hard time telling what scope the variable is in without something like m_ or self. (as in the case of python) on the front of it. It's just a readability nitpick, but at work forgetting m_ or the less common using m_ for local scope variables is punishable by death. >:]

Punishable by death?

The laws must be a bit more relaxed over here in Australia. LOL