I noticed that you are located in Philippines, so I do not have a concrete advice for you as such. However, this is what worked for me in the U.S.: 1. Craigslist's free classified. This leads to small time work first, but it builds up soon after. 2. Meet the clients after the first contact. In my case, it has doubled or tripled my chances of getting a project, once the clients put a face to a name. 3. Repeat business. Make your first impression by delivering a quality product, you will get repeat business. 4. Referrals. Don't feel shy to ask your clients to refer you to others. What did not work for me: Direct mail. I sent out $1200 worth of postcards to a list I purchased. I did not get a single call. Good Luck!

My point in the message to you was that people started writing comments without even clicking on the link. You click on the link you get some more information, may be not a whole lot of explanation, but information it is. Now, about my approach: There could be myriad of reasons why you would want to know the relational linkages. May be you, you were doing a data cleanup, which meant deleting the parent rows, and keeping the child rows by making the foreign key column null, or may even delete cascading, if that is what was needed as a part of the cleanup process. So, unless you know the context, you can say an emphatic "wrongful approach." Do you get my point?

>> If an article is too much then a tip/trick requires less commitment. I don't understand what you mean by that. Anyway, the reason why I developed the script is to see how deep the rabbit hole is. Yes, I can use any reverse engineering ERD tool to see that (Visio is my favorite.) If you have been around as long as I have and have worked on projects where no one really knew the entire system/database, you have to rely on quick and dirty tools like my script to find your way. Visio may or may not be there at your disposal. I really do not understand why people are making smart ass comments about how they do things. Col. Jessep (A few good men) said, "I have neither the time nor the inclination to explain myself to a man who rises and sleeps under the blanket of the very freedom I provide, then questions the manner in which I provide it! I'd rather you just said thank you and went on your way." :)

I was going to curse you out but then saw that you are a legend at The Code Project, so I won't. > Write an article: Yes the link is kinda article and the script itself. > I recommend using referential integrity I hope you are not confusing "on delete cascade" feature in the context of referential integrity. Referential Integrity: NICE On Delete Cascade: BAD (VERY BAD actually)

If you are fanatic about normalization, I am sure you know the pains associated with it. Deletion of a row at a top level table can become a project very quickly due the child tables dependencies, which can run several levels deep. I have a script to do that. Please feel free to download and share.

This may not be exactly what you need, however, you may find some pointers from there. http://www.easydaq.biz[] I acquired a USB relay board from them for $80. Make a note of the chipsets used in the board. Go to the chip manufacturer's site and get some basic information to write your own drivers. Good Luck! :thumbsup: