trying to make a race plan program (program for bets on horses)

Question

1.75/5 (4 votes)

See more:

Hi, I would like to write a program for organizing bets on horses. It's functions should cover all the typical operation at a betting ageny, such as setting up a race, taking bets, calculating the odds, and entering the final results.

What programming language would you advise me to use? Should I use a database, and which? Can you give any additional tips how to go about it?

[edit]Rewrote posting for brevity and clarity. Please check the earlier versions for more details.
Stefan Lang[/edit]

Posted 29-Sep-11 10:03am

willcyrus

Updated 29-Sep-11 22:41pm

Stefan_Lang

v3

Add a Solution

Comments

André Kraak 29-Sep-11 16:06pm

So what is your actual question?

mbue 29-Sep-11 16:28pm

Internal error: Too many numbers in question.

willcyrus 29-Sep-11 16:48pm

which programgramming language i should use that would make it easier

Albert Holguin 29-Sep-11 16:52pm

I'd recommend you shorten your explanation and place your actual question up there ^ ...use the "Improve question" link to make the changes...

Kschuler 29-Sep-11 17:17pm

If you're question is really "Which programming language should I use?" then I'd say it really doesn't matter. You've done the hard part already with planning out exactly how your program is going to work.

Stefan_Lang 30-Sep-11 3:57am

lol, when I read the title I thought this was about race conditions (see http://en.wikipedia.org/wiki/Race_condition#Computing - hey, this is a computing site after all!) Also, 'making a plan about a horse race' sounds a bit like you wish to plan the outcome. Apparently though, your purpose is to 'handle the bets', not 'plan the race'.

Maybe you should change the title to 'trying to make a program for handling bets on horses' ;)

P.S.: I took the liberty to clarify your title and add formatting tags. You still might need to fix your tables, some of the entries' formatting seem to be off.

Stefan_Lang 30-Sep-11 4:49am

I've taken the liberty to rewrite your 'question' into something more tangible. It may not reflect exactly what you were after, so feel free to correct it (use the link 'Improve question'). But, when you do, please spare us all the details - half the terms you used aren't even common knowledge to many people (including myself), and we wouldn't know what to do about them. I for one chose to ignore these parts. You're much more likely to receive a response if you don't choose to pose a question in 'horse-bet-alese'.

willcyrus 1-Oct-11 0:34am

anyone willing to do this program for me ill pay for it?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Stefan_Lang · Answer 1 · 2011-09-29T22:14:00

As a reminder, here's the help text that you should have read when posting your question (emphasis mine):

A few simple rules when posting your question.

    1. Have you searched or Googled for a solution?
    2. Be specific! Don t ask "I need to write a booking application". Specify exactly what it is you need help with.
    3. Keep the subject brief but descriptive. eg "How do I change the dialog colour?"
    4. Keep the question as concise as possible. If you have to include code, include the smallest snippet of code you can - do not dump your entire codebase.
    5. Tag your question appropriately.
    6. Your question may be edited or retagged by others. Anything inappropriate will be removed.
    7. If you have a school or university assignment, assume that your teacher or lecturer is also reading these forums.
    8. Be courteous and DON T SHOUT. Everyone here helps because they enjoy helping others, not because it s their job.
    9. Do not remove or empty a message if others have replied. Keep the thread intact and available for others to search and read.
    10. Do not be abusive, offensive, inappropriate,harass anyone on the boards or post ads or spam. Doing so will get you kicked off and banned. Play nice.