Advice needed on adding checkboxes for a total

I have written most of the easy ASP portion for a MS Access
DB insert. In the database, I have about 15 checkboxes in it. Five
of them represent a point total of 1 point, 5 of them at 2 points each
and 5 at 4 points each. Over time this database will get quite big.
In the database, I will most likely need a field that will represent
the point value of all 15 checkbox fields or I'll just have to use a
formula in all future reports, modify asp's and query asp's to
calculate the 15 checkboxes.

Anyway, can someone suggest which direction I should take (Total Point
Value field in the database or not). The problem that I worried about
with making a Total Point Value field is the formulas processing the
correct point total when the modify.asp changes some or all of the
checkbox values. The problem I have without the field is that future
yearly and monthly reports would be needed and I don't want the report
to be too slow since it will have to process at least 15 checkbox
fields for each record multiplied by tens of thousands of records in
the future.

Any thoughts? TIA

Re: Advice needed on adding checkboxes for a total

"ynott" wrote in message
news:b9fqq01rrht8k8bdg0l8kbido0fpvfoftq@4ax.com...
>I have written most of the easy ASP portion for a MS Access
> DB insert. In the database, I have about 15 checkboxes in it. Five
> of them represent a point total of 1 point, 5 of them at 2 points each
> and 5 at 4 points each. Over time this database will get quite big.
> In the database, I will most likely need a field that will represent
> the point value of all 15 checkbox fields or I'll just have to use a
> formula in all future reports, modify asp's and query asp's to
> calculate the 15 checkboxes.
>
> Anyway, can someone suggest which direction I should take (Total Point
> Value field in the database or not). The problem that I worried about
> with making a Total Point Value field is the formulas processing the
> correct point total when the modify.asp changes some or all of the
> checkbox values. The problem I have without the field is that future
> yearly and monthly reports would be needed and I don't want the report
> to be too slow since it will have to process at least 15 checkbox
> fields for each record multiplied by tens of thousands of records in
> the future.
>
> Any thoughts? TIA

not sure if I understand this correctly, or even if what I suggest will
help...but....

some time ago I did an application that had 15 or 16 checkboxes. these were
to add options to a product. rather than store 15 values (one for each box
checked), I gave the boxes a value.

box 1 = 1
box 2 = 2
box 3 = 4
box 4 = 8
box 5 = 16

etc etc

this meant that for any boxes checked I had a unique number, if that number
was 8, then I knew that only checkbox 4 had been ticked, if it was 6, then
boxes 2 and 3 had been checked, 25 meant boxes 5, 4 and 1 etc.

this way I only had to store one value and from that value I could easily
calculate which boxes had been checked.

like I said, this might not be what you are trying to do.

Re: Advice needed on adding checkboxes for a total

Thanks for the reply, but that won't work for me. Any other thoughts
out there?

On Wed, 1 Dec 2004 09:50:17 -0000, "Alistair"
wrote:

>
>"ynott" wrote in message
>news:b9fqq01rrht8k8bdg0l8kbido0fpvfoftq@4ax.com...
>>I have written most of the easy ASP portion for a MS Access
>> DB insert. In the database, I have about 15 checkboxes in it. Five
>> of them represent a point total of 1 point, 5 of them at 2 points each
>> and 5 at 4 points each. Over time this database will get quite big.
>> In the database, I will most likely need a field that will represent
>> the point value of all 15 checkbox fields or I'll just have to use a
>> formula in all future reports, modify asp's and query asp's to
>> calculate the 15 checkboxes.
>>
>> Anyway, can someone suggest which direction I should take (Total Point
>> Value field in the database or not). The problem that I worried about
>> with making a Total Point Value field is the formulas processing the
>> correct point total when the modify.asp changes some or all of the
>> checkbox values. The problem I have without the field is that future
>> yearly and monthly reports would be needed and I don't want the report
>> to be too slow since it will have to process at least 15 checkbox
>> fields for each record multiplied by tens of thousands of records in
>> the future.
>>
>> Any thoughts? TIA
>
>not sure if I understand this correctly, or even if what I suggest will
>help...but....
>
>some time ago I did an application that had 15 or 16 checkboxes. these were
>to add options to a product. rather than store 15 values (one for each box
>checked), I gave the boxes a value.
>
>box 1 = 1
>box 2 = 2
>box 3 = 4
>box 4 = 8
>box 5 = 16
>
>etc etc
>
>this meant that for any boxes checked I had a unique number, if that number
>was 8, then I knew that only checkbox 4 had been ticked, if it was 6, then
>boxes 2 and 3 had been checked, 25 meant boxes 5, 4 and 1 etc.
>
>this way I only had to store one value and from that value I could easily
>calculate which boxes had been checked.
>
>like I said, this might not be what you are trying to do.
>

Re: Advice needed on adding checkboxes for a total

I'm not your mother so I won't say anything about using Access for this.

If you accessed your inserts and updates through queries, you could have
those queries maintain your TotalPoint Value field for you.

I'd suggest you take a second look at Alistair's suggestion. It's a pretty
good one.

TOm

wrote in message news:kttsq0l0jc3hpm0apgnpu9anh6e508kur8@4ax.com...
> Thanks for the reply, but that won't work for me. Any other thoughts
> out there?
>
> On Wed, 1 Dec 2004 09:50:17 -0000, "Alistair"
> wrote:
>
> >
> >"ynott" wrote in message
> >news:b9fqq01rrht8k8bdg0l8kbido0fpvfoftq@4ax.com...
> >>I have written most of the easy ASP portion for a MS Access
> >> DB insert. In the database, I have about 15 checkboxes in it. Five
> >> of them represent a point total of 1 point, 5 of them at 2 points each
> >> and 5 at 4 points each. Over time this database will get quite big.
> >> In the database, I will most likely need a field that will represent
> >> the point value of all 15 checkbox fields or I'll just have to use a
> >> formula in all future reports, modify asp's and query asp's to
> >> calculate the 15 checkboxes.
> >>
> >> Anyway, can someone suggest which direction I should take (Total Point
> >> Value field in the database or not). The problem that I worried about
> >> with making a Total Point Value field is the formulas processing the
> >> correct point total when the modify.asp changes some or all of the
> >> checkbox values. The problem I have without the field is that future
> >> yearly and monthly reports would be needed and I don't want the report
> >> to be too slow since it will have to process at least 15 checkbox
> >> fields for each record multiplied by tens of thousands of records in
> >> the future.
> >>
> >> Any thoughts? TIA
> >
> >not sure if I understand this correctly, or even if what I suggest will
> >help...but....
> >
> >some time ago I did an application that had 15 or 16 checkboxes. these
were
> >to add options to a product. rather than store 15 values (one for each
box
> >checked), I gave the boxes a value.
> >
> >box 1 = 1
> >box 2 = 2
> >box 3 = 4
> >box 4 = 8
> >box 5 = 16
> >
> >etc etc
> >
> >this meant that for any boxes checked I had a unique number, if that
number
> >was 8, then I knew that only checkbox 4 had been ticked, if it was 6,
then
> >boxes 2 and 3 had been checked, 25 meant boxes 5, 4 and 1 etc.
> >
> >this way I only had to store one value and from that value I could easily
> >calculate which boxes had been checked.
> >
> >like I said, this might not be what you are trying to do.
> >
>

Re: Advice needed on adding checkboxes for a total

Can you elaborate on why you're using 15 different checkboxes and
SPECIFICALLY the information that you're capturing? There's the
possibility that the issue may lay with how your capturing & storing the
data. I realize that will hurt given that you're this far into
development, however the stronger the underlying database scheme the
easier things will be later on - as you're starting to see even now.

David H

ynott wrote:
> Thanks for the reply, but that won't work for me. Any other thoughts
> out there?
>
> On Wed, 1 Dec 2004 09:50:17 -0000, "Alistair"
> wrote:
>
>
>>"ynott" wrote in message
>>news:b9fqq01rrht8k8bdg0l8kbido0fpvfoftq@4ax.com...
>>
>>>I have written most of the easy ASP portion for a MS Access
>>>DB insert. In the database, I have about 15 checkboxes in it. Five
>>>of them represent a point total of 1 point, 5 of them at 2 points each
>>>and 5 at 4 points each. Over time this database will get quite big.
>>>In the database, I will most likely need a field that will represent
>>>the point value of all 15 checkbox fields or I'll just have to use a
>>>formula in all future reports, modify asp's and query asp's to
>>>calculate the 15 checkboxes.
>>>
>>>Anyway, can someone suggest which direction I should take (Total Point
>>>Value field in the database or not). The problem that I worried about
>>>with making a Total Point Value field is the formulas processing the
>>>correct point total when the modify.asp changes some or all of the
>>>checkbox values. The problem I have without the field is that future
>>>yearly and monthly reports would be needed and I don't want the report
>>>to be too slow since it will have to process at least 15 checkbox
>>>fields for each record multiplied by tens of thousands of records in
>>>the future.
>>>
>>>Any thoughts? TIA
>>
>>not sure if I understand this correctly, or even if what I suggest will
>>help...but....
>>
>>some time ago I did an application that had 15 or 16 checkboxes. these were
>>to add options to a product. rather than store 15 values (one for each box
>>checked), I gave the boxes a value.
>>
>>box 1 = 1
>>box 2 = 2
>>box 3 = 4
>>box 4 = 8
>>box 5 = 16
>>
>>etc etc
>>
>>this meant that for any boxes checked I had a unique number, if that number
>>was 8, then I knew that only checkbox 4 had been ticked, if it was 6, then
>>boxes 2 and 3 had been checked, 25 meant boxes 5, 4 and 1 etc.
>>
>>this way I only had to store one value and from that value I could easily
>>calculate which boxes had been checked.
>>
>>like I said, this might not be what you are trying to do.
>>
>
>