That's a PRETTY good point. But at least you agree with me to set the define for each .cpp file and not all of them in one header file. One modification and BAM, at least 15 minutes to compile for one little change!

I was wondering what is the best way to set constanta in C/C++. Using a header file with all constants set as #defines? Kind of like:

#define pi (3.1416f)
#define gravity_m_div_sqrt_secs (9.81f)

Or, set as static members of a class?

// Common.h
#ifndef __COMMON__
#define __COMMON__

class Common{

public:
static float k_pi;
static float k_gravity_m_div_sqrt_secs;

};

// Common.cpp
#include "Common.h"

float Common::k_pi = 3.1416f;
float Common::k_gravity_m_div_sqrt_secs = 9.81f;

It think is better to set 'em as a class, because sometimes you need to access them in any part of the code. And if you modify any one of them, the compilation time will be faster. But then I think how much RAM will these constants will be use, so in that case #defines are useful. I really want to know your opinion.

When I was 15 I worked as a maintenance employee in the City Zoo. I lasted two weeks because my friends that worked with only last one week and I was getting boring. When I was 16 I worked as a clerk in a shitty internet coffee shop(two weeks later the owner has to closed it). Job pretty sucks because you could not work if you wasn't a Christian. I wasn't, but my sister was, so I put her as a reference and the owner knew her. When I was 17 I work for a cousin of mine in two business that he owned (a Blankets and Pillow store shop carrying boxes of blankets from the trailer truck to the storage, and a as clerk in his cell phone depot). I did that for all summers vacations from 2003 to 2008 (senior year of high school and the entire major in college). Shitty pay from Sunday to Sunday (almost 24/7). Right after I graduate from college I worked as support for a factory production software. It kind of sucks because the database, and the forms in C# were a mess, and I didn't like the field and topic of the factory. Also the pay was very low. I lasted a year with them. I gained a lot of experience, though. Now I'm working as Android Developer. The company pays the double than the factory and a little bit more than the factory, and I gaining a lot more experience. I'm developing in two languages, and I use at least 3 script language and several home brew tools.

If the memory and the hardware can handle it, and it doesn't get your pc freeze or stuck you should give it a try.

Well online could be very easier than CHM. The issue is that if the network or the internet is down and the client needs to check the help, how is the client going to do it? I prefer having a local manual than a web site manual. Nothing different from having a brand new ceiling fan with a clear and simple installation manual (I just installed one in my room ;P).

That's used to happen to me when I open the same project twice. And sometime you have load the symbols. The break points are on the pbd files.

Yes, walking away with a pork burrito, diet coke and cigar. Always help.

If you want to share some programming concepts, show him how to make Desktop or Windows apps for a good beginning. Something easy and fast so the kid won't lose any interest.

Your ideas are cool and I'm agree with them but I like to work where I can put things that I like in my desk to personalize it. Also has to have a vending machine with a lot of diet cokes and candy. Also be allow to eat at any time in the desk.

Never because I drink a lot of Diet Cokes :-D and if a I am not coding, I'm in the bathroom taking the dump or peeing, or reading code project ;P .

You are fucking right. Is not an Enterprise solution. -Access is not a Database server. Which means I cannot be use by different computers on different locations. -The information in Access could be copy by any person just by doing copy-paste and anyone who has access could just check the info in your db. Because the info is in plain file with no security at all. Fuck it, recommend MySQL, is for free, (cheaper than Access). Well the server cost a couple of bucks like 60 dlls every year or less. Access could be use by local businesses like Pop's groceries stores, maybe get trace or save records of a local raffles in your town fair or school practices for developer students. I remember when I have to do a Convention Register Web app with text files, are fucking kidding me? Text files. It barely worked. But it worked because we only used it for one day and we use a server. So I can understand your pain my friend. You have to let them know that Access is Mothafucking bullshit as on security as on performance. It crashes a lot if is used by many people. I cannot response to several request (like search, and data manipulation) at the same time, so you can tell your clients that this performance issue will affect their data and it will cost them money.

Because C# is similar to Java. So if newbies get C#, java would be a piece of cake in a near future. Don't get me wrong, VB is very useful when user has to do or use some scripts or macros on office, and can make your life easier. But if you are developing a new software C# is better, because its syntax is less complicated.