Cumulative Queries with a twist

[Guest]

Good morning
I've got some pretty hefty spreadsheets that have the calculations replicated for each spreadsheet. So, rather than inserting the calculations all the time, I'd like to just import each table when I need to, and let the query do its thing

An explanation: my company is a large distribitor of product with specific attributes according to its destination. However, we know that I can fit 30 units per case and that if an order calls for a full number of cases, I can select the case. If it calls for remainders, I can select them either 3, 2, or 1 to my arm (to assist with batching). When I will hit or pass 12 units accummulated to my arm, I will take them either 6, 2, or 1 and put them in the case on the conveyor.

My table is
LOA
STO
DEPT/STAT
SLO
PIECE

For example
0101 01 CC 00111
0101 01 CC 00112 2
0101 01 CC 00113

The query only needs to be geared toward pieces. Here's the SQL so far
SELECT Cigs.Pieces, Int([pieces]/30)+IIf([pieces]/30-(Int([pieces]/30))>0.5,1,0) AS Countcases, Abs([pieces]-[countcases]*30) AS RemfromCases, Int([remfromcases]/3) AS 3toarm, Int(([remfromcases]-(3*Int([remfromcases]/3)))/2) AS 2toarm, [remfromcases]-3*Int([remfromcases]/3)-2*Int(([remfromcases]-(3*Int([remfromcases]/3)))/2) AS 1toar
FROM Cigs

This gets the product to my arm. However, I need to use the logic in the explanation above to determine when and how many units will be cased.

I know that this can be done in Reports. However, I need it done in Queries

This is to determine how often (probability) a particular arm move will occur

Can someone please help
Derek

 

[Tom Ellison]

Dear Derek:

Just getting back after a week away. I'm beginning to see some of
what you want, but I'm really not up to speed on your problem yet.

OK, a "remainder" is a partial case, right?

So, these odd lots accumulate until you have 12 or more items. Then
you are going to put 6, 2, or 1 of them into the currently open case.
Am I close? And how do you decide how many?

I think this will take some study just to understand, but I expect a
solution will be possible.

So, are you still interested?

FYI, I have done some work to pallet shipments that may be not
unsimilar, in that there were a large number of products which pallet
exactly the same, like you are doing cases of 30, we are doing pallets
of 48 or 60 mixed items.

Tom Ellison
Microsoft Access MVP
Ellison Enterprises - Your One Stop IT Experts

 

[Guest]

Sorry, Tom, I was out on travel all last week and have just returned. I appreciate your getting back to me on this one

It could definitely be similar to palletizing. I'll address your questions from within to avoid having to scroll back and forth

----- Tom Ellison wrote: ----

Dear Derek

Just getting back after a week away. I'm beginning to see some o
what you want, but I'm really not up to speed on your problem yet

OK, a "remainder" is a partial case, right

DW: Yes, a remainder is a partial case. The caveat is that if the quantity needed is > 14, a case is used and the difference is returned back to stock. (i.e. getting a case and returning 12 is deemed more efficient than selecting 18 by 3s, 2s, or singles)

So, these odd lots accumulate until you have 12 or more items. The
you are going to put 6, 2, or 1 of them into the currently open case
Am I close? And how do you decide how many

DW: I take my quantity (X) and will put the greatest amount into a case (from the list of 6, 2, or 1) and do the same until I have cleared the entire accummulation. I.e. if I have 11, I put in 6, 2, 2, 1, taking 4 arm motions. It's similar to a different number system (base 8 or hexadecimal), except that the places are based on these numbers instead of a constant. For example:

1 = 00
2 = 01
3 = 01
4 = 02
5 = 02
6 = 10
7 = 10
8 = 11
9 = 11
10 = 12
11 = 12
12 = 20
13 = 20
14 = 21
15 = 21

With the caveat above, the remainder should never > 15. However, if I have 11 in my arm, then have a hit (slot) for 15, I will put the 11 in my case, then get the 15. Since I need to clear my arm immediately, the logic is that I will still put to arm (although > 12) with the assumption that I can do a 2,1,1 as in the table above. By pulling from the slot directly to my case, I am limited to 3,3,3,3,3. Doing so saves me 1/3 of a second for each 15 cartons. Doesn't sound like much, but it results in a savings of 1.25 manhour per day. That covers the depreciation of a new forklift, roughly

I think this will take some study just to understand, but I expect
solution will be possible

So, are you still interested

DW: You bet! I'm already on another thing simultaneously as well, but working between them..

Thanks again
Dere

FYI, I have done some work to pallet shipments that may be no
unsimilar, in that there were a large number of products which palle
exactly the same, like you are doing cases of 30, we are doing pallet
of 48 or 60 mixed items

Tom Elliso
Microsoft Access MV
Ellison Enterprises - Your One Stop IT Expert


On Tue, 6 Apr 2004 06:56:08 -0700, "Derek Wittman

Good morning
I've got some pretty hefty spreadsheets that have the calculations replicated for each spreadsheet. So, rather than inserting the calculations all the time, I'd like to just import each table when I need to, and let the query do its thing

An explanation: my company is a large distribitor of product with specific attributes according to its destination. However, we know that I can fit 30 units per case and that if an order calls for a full number of cases, I can select the case. If it calls for remainders, I can select them either 3, 2, or 1 to my arm (to assist with batching). When I will hit or pass 12 units accummulated to my arm, I will take them either 6, 2, or 1 and put them in the case on the conveyor.
My table is LOA
STO
DEPT/STAT
SLO
PIECE
For example

0101 01 CC 00111
0101 01 CC 00112 2
0101 01 CC 00113

The query only needs to be geared toward pieces. Here's the SQL so far

SELECT Cigs.Pieces, Int([pieces]/30)+IIf([pieces]/30-(Int([pieces]/30))>0.5,1,0) AS Countcases, Abs([pieces]-[countcases]*30) AS RemfromCases, Int([remfromcases]/3) AS 3toarm, Int(([remfromcases]-(3*Int([remfromcases]/3)))/2) AS 2toarm, [remfromcases]-3*Int([remfromcases]/3)-2*Int(([remfromcases]-(3*Int([remfromcases]/3)))/2) AS 1toar
FROM Cigs;

This gets the product to my arm. However, I need to use the logic in the explanation above to determine when and how many units will be cased.
I know that this can be done in Reports. However, I need it done in Queries.
This is to determine how often (probability) a particular arm move will occur.
Can someone please help?

Derek

 

[Tom Ellison]

Dear Derek:

I'll be back on this later. Have to make a study of your requirements
first.

Tom Ellison
Microsoft Access MVP
Ellison Enterprises - Your One Stop IT Experts

Sorry, Tom, I was out on travel all last week and have just returned. I appreciate your getting back to me on this one.

It could definitely be similar to palletizing. I'll address your questions from within to avoid having to scroll back and forth.

----- Tom Ellison wrote: -----

Dear Derek:

Just getting back after a week away. I'm beginning to see some of
what you want, but I'm really not up to speed on your problem yet.

OK, a "remainder" is a partial case, right?

DW: Yes, a remainder is a partial case. The caveat is that if the quantity needed is > 14, a case is used and the difference is returned back to stock. (i.e. getting a case and returning 12 is deemed more efficient than selecting 18 by 3s, 2s, or singles).

So, these odd lots accumulate until you have 12 or more items. Then
you are going to put 6, 2, or 1 of them into the currently open case.
Am I close? And how do you decide how many?

DW: I take my quantity (X) and will put the greatest amount into a case (from the list of 6, 2, or 1) and do the same until I have cleared the entire accummulation. I.e. if I have 11, I put in 6, 2, 2, 1, taking 4 arm motions. It's similar to a different number system (base 8 or hexadecimal), except that the places are based on these numbers instead of a constant. For example:

1 = 001
2 = 010
3 = 011
4 = 020
5 = 021
6 = 100
7 = 101
8 = 110
9 = 111
10 = 120
11 = 121
12 = 200
13 = 201
14 = 210
15 = 211

With the caveat above, the remainder should never > 15. However, if I have 11 in my arm, then have a hit (slot) for 15, I will put the 11 in my case, then get the 15. Since I need to clear my arm immediately, the logic is that I will still put to arm (although > 12) with the assumption that I can do a 2,1,1 as in the table above. By pulling from the slot directly to my case, I am limited to 3,3,3,3,3. Doing so saves me 1/3 of a second for each 15 cartons. Doesn't sound like much, but it results in a savings of 1.25 manhour per day. That covers the depreciation of a new forklift, roughly.

I think this will take some study just to understand, but I expect a
solution will be possible.

So, are you still interested?

DW: You bet! I'm already on another thing simultaneously as well, but working between them...

Thanks again!
Derek

FYI, I have done some work to pallet shipments that may be not
unsimilar, in that there were a large number of products which pallet
exactly the same, like you are doing cases of 30, we are doing pallets
of 48 or 60 mixed items.

Tom Ellison
Microsoft Access MVP
Ellison Enterprises - Your One Stop IT Experts

Good morning,
I've got some pretty hefty spreadsheets that have the calculations replicated for each spreadsheet. So, rather than inserting the calculations all the time, I'd like to just import each table when I need to, and let the query do its thing.

An explanation: my company is a large distribitor of product with specific attributes according to its destination. However, we know that I can fit 30 units per case and that if an order calls for a full number of cases, I can select the case. If it calls for remainders, I can select them either 3, 2, or 1 to my arm (to assist with batching). When I will hit or pass 12 units accummulated to my arm, I will take them either 6, 2, or 1 and put them in the case on the conveyor.
My table is: LOAD
STOP
DEPT/STATE
SLOT
PIECES
For example:

0101 01 CC 00111 5
0101 01 CC 00112 24
0101 01 CC 00113 5

The query only needs to be geared toward pieces. Here's the SQL so far:

SELECT Cigs.Pieces, Int([pieces]/30)+IIf([pieces]/30-(Int([pieces]/30))>0.5,1,0) AS Countcases, Abs([pieces]-[countcases]*30) AS RemfromCases, Int([remfromcases]/3) AS 3toarm, Int(([remfromcases]-(3*Int([remfromcases]/3)))/2) AS 2toarm, [remfromcases]-3*Int([remfromcases]/3)-2*Int(([remfromcases]-(3*Int([remfromcases]/3)))/2) AS 1toarm
FROM Cigs;

This gets the product to my arm. However, I need to use the logic in the explanation above to determine when and how many units will be cased.
I know that this can be done in Reports. However, I need it done in Queries.
This is to determine how often (probability) a particular arm move will occur.
Can someone please help?

Derek

 

[Guest]

Thanks, Tom. The requirements are pretty finicky. Mostly because I am. At the time we set up the logic behind things, there were 4 of us in the company with the skills to do these (Engineered Labor Standards). Now, there are 2, but I'm the Lone Ranger on it (the other is involved in material handling projects while I get systems and reporting tools)

We've been doing this for 4 1/2 years with Excel, creating oodles of 20+Mb workbooks, but to have the logic all in and just have to import a data file. Can save HOURS of my time - yes, it's personal

So, if you have questions, please let me know. I'm happy to help
Dere

----- Tom Ellison wrote: ----

Dear Derek

I'll be back on this later. Have to make a study of your requirement
first

Tom Elliso
Microsoft Access MV
Ellison Enterprises - Your One Stop IT Expert


On Tue, 20 Apr 2004 06:01:09 -0700, "Derek Wittman

Sorry, Tom, I was out on travel all last week and have just returned. I appreciate your getting back to me on this one

It could definitely be similar to palletizing. I'll address your questions from within to avoid having to scroll back and forth
----- Tom Ellison wrote: ----
Dear Derek
Just getting back after a week away. I'm beginning to see some o

what you want, but I'm really not up to speed on your problem yet

OK, a "remainder" is a partial case, right
DW: Yes, a remainder is a partial case. The caveat is that if the quantity needed is > 14, a case is used and the difference is returned back to stock. (i.e. getting a case and returning 12 is deemed more efficient than selecting 18 by 3s, 2s, or singles)
So, these odd lots accumulate until you have 12 or more items. The

you are going to put 6, 2, or 1 of them into the currently open case
Am I close? And how do you decide how many

DW: I take my quantity (X) and will put the greatest amount into a case (from the list of 6, 2, or 1) and do the same until I have cleared the entire accummulation. I.e. if I have 11, I put in 6, 2, 2, 1, taking 4 arm motions. It's similar to a different number system (base 8 or hexadecimal), except that the places are based on these numbers instead of a constant. For example:
1 = 00

2 = 01
3 = 01
4 = 02
5 = 02
6 = 10
7 = 10
8 = 11
9 = 11
10 = 12
11 = 12
12 = 20
13 = 20
14 = 21
15 = 21

With the caveat above, the remainder should never > 15. However, if I have 11 in my arm, then have a hit (slot) for 15, I will put the 11 in my case, then get the 15. Since I need to clear my arm immediately, the logic is that I will still put to arm (although > 12) with the assumption that I can do a 2,1,1 as in the table above. By pulling from the slot directly to my case, I am limited to 3,3,3,3,3. Doing so saves me 1/3 of a second for each 15 cartons. Doesn't sound like much, but it results in a savings of 1.25 manhour per day. That covers the depreciation of a new forklift, roughly
I think this will take some study just to understand, but I expect solution will be possible
So, are you still interested
DW: You bet! I'm already on another thing simultaneously as well, but working between them..
Thanks again Dere
FYI, I have done some work to pallet shipments that may be no

unsimilar, in that there were a large number of products which palle
exactly the same, like you are doing cases of 30, we are doing pallet
of 48 or 60 mixed items

Tom Elliso

Microsoft Access MV
Ellison Enterprises - Your One Stop IT Expert

Good morning

I've got some pretty hefty spreadsheets that have the calculations replicated for each spreadsheet. So, rather than inserting the calculations all the time, I'd like to just import each table when I need to, and let the query do its thing

An explanation: my company is a large distribitor of product with specific attributes according to its destination. However, we know that I can fit 30 units per case and that if an order calls for a full number of cases, I can select the case. If it calls for remainders, I can select them either 3, 2, or 1 to my arm (to assist with batching). When I will hit or pass 12 units accummulated to my arm, I will take them either 6, 2, or 1 and put them in the case on the conveyor.
My table is: LOAD
STOP
DEPT/STATE
SLOT
PIECES
For example:

0101 01 CC 00111 5
0101 01 CC 00112 24
0101 01 CC 00113 5

The query only needs to be geared toward pieces. Here's the SQL so far:

SELECT Cigs.Pieces, Int([pieces]/30)+IIf([pieces]/30-(Int([pieces]/30))>0.5,1,0) AS Countcases, Abs([pieces]-[countcases]*30) AS RemfromCases, Int([remfromcases]/3) AS 3toarm, Int(([remfromcases]-(3*Int([remfromcases]/3)))/2) AS 2toarm, [remfromcases]-3*Int([remfromcases]/3)-2*Int(([remfromcases]-(3*Int([remfromcases]/3)))/2) AS 1toarm
FROM Cigs;

This gets the product to my arm. However, I need to use the logic in the explanation above to determine when and how many units will be cased.
I know that this can be done in Reports. However, I need it done in Queries.
This is to determine how often (probability) a particular arm move will occur.
Can someone please help?

Derek

 

[Tom Ellison]

Dear Derek:

I have studied what you sent, and have a pretty good feel for it I
think.

What you are doing is not probably of very general interest, and I
think we can handle it better with a bit of direct contact. Would
that be agreeable? If so, please reply directly to my email address
as shown in my postings.

Tom Ellison
Microsoft Access MVP
Ellison Enterprises - Your One Stop IT Experts

Thanks, Tom. The requirements are pretty finicky. Mostly because I am. At the time we set up the logic behind things, there were 4 of us in the company with the skills to do these (Engineered Labor Standards). Now, there are 2, but I'm the Lone Ranger on it (the other is involved in material handling projects while I get systems and reporting tools).

We've been doing this for 4 1/2 years with Excel, creating oodles of 20+Mb workbooks, but to have the logic all in and just have to import a data file. Can save HOURS of my time - yes, it's personal.

So, if you have questions, please let me know. I'm happy to help!
Derek

----- Tom Ellison wrote: -----

Dear Derek:

I'll be back on this later. Have to make a study of your requirements
first.

Tom Ellison
Microsoft Access MVP
Ellison Enterprises - Your One Stop IT Experts

Sorry, Tom, I was out on travel all last week and have just returned. I appreciate your getting back to me on this one.

It could definitely be similar to palletizing. I'll address your questions from within to avoid having to scroll back and forth.
----- Tom Ellison wrote: -----
Dear Derek:
Just getting back after a week away. I'm beginning to see some of

what you want, but I'm really not up to speed on your problem yet.

OK, a "remainder" is a partial case, right?
DW: Yes, a remainder is a partial case. The caveat is that if the quantity needed is > 14, a case is used and the difference is returned back to stock. (i.e. getting a case and returning 12 is deemed more efficient than selecting 18 by 3s, 2s, or singles).
So, these odd lots accumulate until you have 12 or more items. Then

you are going to put 6, 2, or 1 of them into the currently open case.
Am I close? And how do you decide how many?

DW: I take my quantity (X) and will put the greatest amount into a case (from the list of 6, 2, or 1) and do the same until I have cleared the entire accummulation. I.e. if I have 11, I put in 6, 2, 2, 1, taking 4 arm motions. It's similar to a different number system (base 8 or hexadecimal), except that the places are based on these numbers instead of a constant. For example:
1 = 001

2 = 010
3 = 011
4 = 020
5 = 021
6 = 100
7 = 101
8 = 110
9 = 111
10 = 120
11 = 121
12 = 200
13 = 201
14 = 210
15 = 211

With the caveat above, the remainder should never > 15. However, if I have 11 in my arm, then have a hit (slot) for 15, I will put the 11 in my case, then get the 15. Since I need to clear my arm immediately, the logic is that I will still put to arm (although > 12) with the assumption that I can do a 2,1,1 as in the table above. By pulling from the slot directly to my case, I am limited to 3,3,3,3,3. Doing so saves me 1/3 of a second for each 15 cartons. Doesn't sound like much, but it results in a savings of 1.25 manhour per day. That covers the depreciation of a new forklift, roughly.
I think this will take some study just to understand, but I expect a solution will be possible.
So, are you still interested?
DW: You bet! I'm already on another thing simultaneously as well, but working between them...
Thanks again! Derek
FYI, I have done some work to pallet shipments that may be not

unsimilar, in that there were a large number of products which pallet
exactly the same, like you are doing cases of 30, we are doing pallets
of 48 or 60 mixed items.

Tom Ellison

Microsoft Access MVP
Ellison Enterprises - Your One Stop IT Experts

Good morning,
I've got some pretty hefty spreadsheets that have the calculations replicated for each spreadsheet. So, rather than inserting the calculations all the time, I'd like to just import each table when I need to, and let the query do its thing.
An explanation: my company is a large distribitor of product with specific attributes according to its destination. However, we know that I can fit 30 units per case and that if an order calls for a full number of cases, I can select the case. If it calls for remainders, I can select them either 3, 2, or 1 to my arm (to assist with batching). When I will hit or pass 12 units accummulated to my arm, I will take them either 6, 2, or 1 and put them in the case on the conveyor.
My table is:
LOAD
STOP
DEPT/STATE
SLOT
PIECES
For example:
0101 01 CC 00111 5
0101 01 CC 00112 24
0101 01 CC 00113 5
The query only needs to be geared toward pieces. Here's the SQL so far:
SELECT Cigs.Pieces, Int([pieces]/30)+IIf([pieces]/30-(Int([pieces]/30))>0.5,1,0) AS Countcases, Abs([pieces]-[countcases]*30) AS RemfromCases, Int([remfromcases]/3) AS 3toarm, Int(([remfromcases]-(3*Int([remfromcases]/3)))/2) AS 2toarm, [remfromcases]-3*Int([remfromcases]/3)-2*Int(([remfromcases]-(3*Int([remfromcases]/3)))/2) AS 1toarm
FROM Cigs;
This gets the product to my arm. However, I need to use the logic in the explanation above to determine when and how many units will be cased.
I know that this can be done in Reports. However, I need it done in Queries.
This is to determine how often (probability) a particular arm move will occur.
Can someone please help?
Derek

 

[Guest]

Tom
I agree that it's probably a rarity of a function that I am trying to perform here - as with my post Multiple-Record queries on 4/19. I'd be happy to take this discussion offline in the interest of saving the time of other readers of the ng

Thanks
Dere

----- Tom Ellison wrote: ----

Dear Derek

I have studied what you sent, and have a pretty good feel for it
think

What you are doing is not probably of very general interest, and
think we can handle it better with a bit of direct contact. Woul
that be agreeable? If so, please reply directly to my email addres
as shown in my postings

Tom Elliso
Microsoft Access MV
Ellison Enterprises - Your One Stop IT Expert


On Tue, 20 Apr 2004 14:26:02 -0700, "Derek Wittman

Thanks, Tom. The requirements are pretty finicky. Mostly because I am. At the time we set up the logic behind things, there were 4 of us in the company with the skills to do these (Engineered Labor Standards). Now, there are 2, but I'm the Lone Ranger on it (the other is involved in material handling projects while I get systems and reporting tools)

We've been doing this for 4 1/2 years with Excel, creating oodles of 20+Mb workbooks, but to have the logic all in and just have to import a data file. Can save HOURS of my time - yes, it's personal
So, if you have questions, please let me know. I'm happy to help Dere
----- Tom Ellison wrote: ----
Dear Derek
I'll be back on this later. Have to make a study of your requirement first
Tom Elliso

Microsoft Access MV
Ellison Enterprises - Your One Stop IT Expert

Sorry, Tom, I was out on travel all last week and have just returned. I appreciate your getting back to me on this one
It could definitely be similar to palletizing. I'll address your questions from within to avoid having to scroll back and forth
----- Tom Ellison wrote: ----
Dear Derek
Just getting back after a week away. I'm beginning to see some o

what you want, but I'm really not up to speed on your problem yet

OK, a "remainder" is a partial case, right
DW: Yes, a remainder is a partial case. The caveat is that if the quantity needed is > 14, a case is used and the difference is returned back to stock. (i.e. getting a case and returning 12 is deemed more efficient than selecting 18 by 3s, 2s, or singles)
So, these odd lots accumulate until you have 12 or more items. The

you are going to put 6, 2, or 1 of them into the currently open case
Am I close? And how do you decide how many

DW: I take my quantity (X) and will put the greatest amount into a case (from the list of 6, 2, or 1) and do the same until I have cleared the entire accummulation. I.e. if I have 11, I put in 6, 2, 2, 1, taking 4 arm motions. It's similar to a different number system (base 8 or hexadecimal), except that the places are based on these numbers instead of a constant. For example:
1 = 00

2 = 01
3 = 01
4 = 02
5 = 02
6 = 10
7 = 10
8 = 11
9 = 11
10 = 12
11 = 12
12 = 20
13 = 20
14 = 21
15 = 21

With the caveat above, the remainder should never > 15. However, if I have 11 in my arm, then have a hit (slot) for 15, I will put the 11 in my case, then get the 15. Since I need to clear my arm immediately, the logic is that I will still put to arm (although > 12) with the assumption that I can do a 2,1,1 as in the table above. By pulling from the slot directly to my case, I am limited to 3,3,3,3,3. Doing so saves me 1/3 of a second for each 15 cartons. Doesn't sound like much, but it results in a savings of 1.25 manhour per day. That covers the depreciation of a new forklift, roughly
I think this will take some study just to understand, but I expect a solution will be possible.
So, are you still interested?
DW: You bet! I'm already on another thing simultaneously as well, but working between them...
Thanks again! Derek
FYI, I have done some work to pallet shipments that may be not

unsimilar, in that there were a large number of products which pallet
exactly the same, like you are doing cases of 30, we are doing pallets
of 48 or 60 mixed items.

Tom Ellison

Microsoft Access MVP
Ellison Enterprises - Your One Stop IT Experts

Good morning,
I've got some pretty hefty spreadsheets that have the calculations replicated for each spreadsheet. So, rather than inserting the calculations all the time, I'd like to just import each table when I need to, and let the query do its thing.
An explanation: my company is a large distribitor of product with specific attributes according to its destination. However, we know that I can fit 30 units per case and that if an order calls for a full number of cases, I can select the case. If it calls for remainders, I can select them either 3, 2, or 1 to my arm (to assist with batching). When I will hit or pass 12 units accummulated to my arm, I will take them either 6, 2, or 1 and put them in the case on the conveyor.
My table is:
LOAD
STOP
DEPT/STATE
SLOT
PIECES
For example:
0101 01 CC 00111 5
0101 01 CC 00112 24
0101 01 CC 00113 5
The query only needs to be geared toward pieces. Here's the SQL so far:
SELECT Cigs.Pieces, Int([pieces]/30)+IIf([pieces]/30-(Int([pieces]/30))>0.5,1,0) AS Countcases, Abs([pieces]-[countcases]*30) AS RemfromCases, Int([remfromcases]/3) AS 3toarm, Int(([remfromcases]-(3*Int([remfromcases]/3)))/2) AS 2toarm, [remfromcases]-3*Int([remfromcases]/3)-2*Int(([remfromcases]-(3*Int([remfromcases]/3)))/2) AS 1toarm
FROM Cigs;
This gets the product to my arm. However, I need to use the logic in the explanation above to determine when and how many units will be cased.
I know that this can be done in Reports. However, I need it done in Queries.
This is to determine how often (probability) a particular arm move will occur.
Can someone please help?
Derek