How "Other" wagers work using the Selections and Wagers View

I had thought that I had documented this, but couldn't find it when I looked. I
probably avoided documenting it because it is pretty retarded, relatively speaking
of course - it is a very, err, challenged implimentation. The bottom line is that when
you create a wager of type "other" the wager is really only available for storing to a
database during that session (before you shut ES down, or close the card you are working on).
So, to use an Other type wager this is what you would do:

A) Results at this point are in and you have a results file.
B) You load up the card you want.
C) You go to the wagers and selections screen -- perhaps you've already made the wagers
(including the "other" type wager), perhaps not. Its not important. What is important
is that you make them now.
D) At this point, when you make your "other" type wager, you manually fill in the
number of tickets (number of plays on a ticket, if you will), and the total return for the
wager. Note that this info is wholly generated for you by ES for all of the natively supported
wager types.
E) You then connect to the database you want to store the wager in (if not connected already),
and do the old "store to database" trick.

The major concept here: If you have wagers that are the "other" type then you MUST enter
in the number of tickets (to generate cost of the wager) AND the return from
the wager right before you store to database. NOTE that this means that you can NOT use
"other" type wagers AND use "store by track" because "store by track" opens the card(s), does what it needs to do,
stores it, and then closes it -- you don't get a chance to enter in your other type wagers.


There are a couple of reasons for this rather shoddy implementation. I won't elaborate, but will list:
A) I don't like the way that multi race results are presented in the results files. The
implementation, at least for me, was not straight forward so I did not spend the time this go
around implementing it "native" support for them.

B) I decided that "Other" would take care of such things as multi-race wagers - AFTER the original
design of the database. The original database does not have all of the necessary places to
better support the "other" wager type.