Function in Query

H

Hardhit

Hello All,

I have a query in which I use a function to calculate the quantity that
needs to be ordered based on the stock and the demands of a customer.
The query run's fine the first time I start the database but when I scroll
in the query window I get different quantities that are displayed in the
column where the function is used. Also when I close the query and run it
again I get wrong restuls.

See here the function that I have written.

Option Compare Database

Dim dDifference As Double
Dim strOldPn As String

Function OrderQtyCalc(strPartNr As String, dOrderQty As Double, dPackSize As
Double)
Dim dBoxes As Double
Dim dCalc As Double


If strOldPn = strPartNr Then

dCalc = dDifference - dOrderQty
If dCalc < 0 Then
dBoxes = Round((-dCalc / dPackSize) + 0.5, 0)
OrderQtyCalc = dBoxes * dPackSize
Else
dBoxes = 0
OrderQtyCalc = 0

End If

dDifference = dDifference + (dBoxes * dPackSize) - dOrderQty

Else

dDifference = 0
strOldPn = strPartNr

dCalc = dDifference - dOrderQty
If dCalc < 0 Then
dBoxes = Round((-dCalc / dPackSize) + 0.5, 0)
OrderQtyCalc = dBoxes * dPackSize
Else
dBoxes = 0
OrderQtyCalc = 0

End If

dDifference = dDifference + (dBoxes * dPackSize) - dOrderQty

End If

End Function

And this is the SQL of the query.

SELECT Query1.PoNr, Query1.SupplName, Query1.PartNr, Query1.Date,
OrderQtyCalc([PartNr],[SumOfSumOfOrderQty],[PackQty]) AS OrderQty
FROM Query1
WHERE (((OrderQtyCalc([PartNr],[SumOfSumOfOrderQty],[PackQty]))>0))
ORDER BY Query1.Date;


What is wrong with my code ? I think it has something to do with the public
variable dDifference that I have but I can't get the correct results without
this variable as I need to retain the result of the last calculation for the
next iteration of the query.

How can I get around this problem ?

Regards,
Peter
 
M

Michel Walsh

The function is call as needed, each time the record has to be displayed. IT
IS NOT CALLED once for all, before the end of the query. So, since it seems
it depends on what was previously computed, the computation depends on what
was previously DISPLAYED. In short, if 10 records are displayed, then the
function is only called 10 times (roughly, and can be more if you use the
function more than once in the select query).

You can FIX that value returned by the function by inserting (with an
insert query) all the rows into a temporary table, and THEN read the
temporary table.



Hoping it may help,
Vanderghast, Access MVP
 
A

Amy Blankenship

Hardhit said:
Hello All,

I have a query in which I use a function to calculate the quantity that
needs to be ordered based on the stock and the demands of a customer.
The query run's fine the first time I start the database but when I scroll
in the query window I get different quantities that are displayed in the
column where the function is used. Also when I close the query and run it
again I get wrong restuls.

See here the function that I have written.

Option Compare Database

Dim dDifference As Double
Dim strOldPn As String
Click to expand...


It seems to me that what you're trying to accomplish here is that these
values start at 0 or "", but then as the query runs you do stuff to them.
When you have run the query once, these then will start at some other value.

You may find that you can fix this by adding a field to your query that
checks if this is the last record (what this looks like will be different
depending on what the query is) and pass that as a parameter. You can then
set your variables empty at the end of the function when that is true.

It looks, though, like you could simply handle this in an ordinary query (or
several that are chained).

HTH;

Amy
 
H

Hardhit

Hi Amy,

Can you start me on the right way on how to check for the last record ?
I have tried to do this in simple queries but I'm not getting the results
wanted. Therefore I used the function.
This gives me the correct results but only the first time the quety is run
after starting the program.

I indeed have an issue with the value of dDifference not being 0 at the
start of the query the next time around.
So if you could start me on the right way of checking how to set the value
to 0 and "" when running the query.

Regards,
Peter
 
A

Amy Blankenship

Hardhit said:
Hi Amy,

Can you start me on the right way on how to check for the last record ?
I have tried to do this in simple queries but I'm not getting the results
wanted. Therefore I used the function.
This gives me the correct results but only the first time the quety is run
after starting the program.

I indeed have an issue with the value of dDifference not being 0 at the
start of the query the next time around.
So if you could start me on the right way of checking how to set the value
to 0 and "" when running the query.
Click to expand...

What's your table structure?
 
A

Amy Blankenship

Hardhit said:
Hi Amy,

Can you start me on the right way on how to check for the last record ?
I have tried to do this in simple queries but I'm not getting the results
wanted. Therefore I used the function.
This gives me the correct results but only the first time the quety is run
after starting the program.

I indeed have an issue with the value of dDifference not being 0 at the
start of the query the next time around.
So if you could start me on the right way of checking how to set the value
to 0 and "" when running the query.
Click to expand...

Oh, and what's the text of your existing query?

BTW, the simplest way to handle this is just to use code (a macro or sub) to
run the query, and initialize those vars prior to running it.
 
H

Hardhit

Hello Amy,

The SQL is :

SELECT Query1.PoNr, Query1.SupplName, Query1.PartNr, Query1.Date,
OrderQtyCalc([PartNr],[SumOfSumOfOrderQty],[PackQty]) AS OrderQty
FROM Query1
WHERE (((OrderQtyCalc([PartNr],[SumOfSumOfOrderQty],[PackQty]))>0))
ORDER BY Query1.Date;

This query is based on another query which joins the Supplier table, The
parts Table, The POHeader table, The Orders Table and the BOM table.
In the query used above I select the PoNr and PackQty from the PO table, the
PartNr from the Parts Table, the Date and the OderQty from the Customer
Order table this is all attached to the BOM table in which I then calculate
the OrderQty based on the the number of times a part is used in an assembly
which is in the BOM table. This all results in a query which has the
following info.

PoNr (Number field)
SupplName (Text field)
PartNr (Text field)
Date (Date field)
SumOfSumOfOrderQty (number field) which is a calculated field of Customer
Assy OrderQty * BOMQty of Part used in Assy
PackQty (number field)

Regards,
Peter
 
A

Amy Blankenship

Hardhit said:
Hello Amy,

The SQL is :

SELECT Query1.PoNr, Query1.SupplName, Query1.PartNr, Query1.Date,
OrderQtyCalc([PartNr],[SumOfSumOfOrderQty],[PackQty]) AS OrderQty
FROM Query1
WHERE (((OrderQtyCalc([PartNr],[SumOfSumOfOrderQty],[PackQty]))>0))
ORDER BY Query1.Date;

This query is based on another query which joins the Supplier table, The
parts Table, The POHeader table, The Orders Table and the BOM table.
In the query used above I select the PoNr and PackQty from the PO table,
the PartNr from the Parts Table, the Date and the OderQty from the
Customer Order table this is all attached to the BOM table in which I then
calculate the OrderQty based on the the number of times a part is used in
an assembly which is in the BOM table. This all results in a query which
has the following info.
Click to expand...

The problem is that your WHERE clause also uses your function, which makes
it impossible to use a "ranking" subquery to determine if you are on your
first or last record.

Let me try to state, in words, what I see your logic doing, and let's see if
we can come up with a way to do it with just one or more queries.

On each row (ordered by date)
-if this is the same part number as the previous row
-look at how much we have
-check to see if subtracting the quantity of the order results in a
negative number
-yes
-divide the amount we're short by the pack quantity,
multiply by .5
-multiply that again by the pack quantity, this is our
result
-no
reset all variables
return 0

-not the same part number
-reset variables
-perform above steps from -look at how much...

It looks to me like you've been very lucky, since you're not sorting by part
number. Your part numbers may not always be contiguous, which I would
expect to throw your numbers off big time. It also looks to me that the
only time you will _not_ have a quantity to order is if there is an order
quantity of zero.

I have some ideas of where to take this, but I don't want to invest too much
time into this until I can see what the end goal is here, not the particular
implementation that you've chosen to try.

-Amy
 
H

Hardhit

Hello Amy,

The problem with the partnumber not being sorted I discovered yesterday when I wanted to test the results of the function when running it trhough all the partnumbers to order. I didn't have this issue before since I was only testing with 1 partnumber.
However I put a sort on the partnumber and this resolved that issue.

What I want to do is to check if I have enough parts to build my next demand (checking the negative value) if the value is positive then I have enough parts and I don't need to order the parts for that customer order. If the value is negative then I determine the number of boxes to order by deviding the negaive result by the packsize so that when I do the order I always order quantity's based on the box packsize.

Also I'm not multiplying by 0.5 but I'm adding 0.5 to the result of the negative number devided by the packsize this to make sure that my box quantity is rounded upward.

dBoxes = Round((-dCalc / dPackSize) + 0.5, 0) 'Make sure that the number of boxes is rounded upward

This is the result that the query is giving which is correct.

PoNr SupplName PartNr DelivDate SumOfOrderQty PackQty OrderQty
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 1/01/2001 14580 4.300,00 17.200,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 25/04/2008 2300 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 29/04/2008 900 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 5/05/2008 3600 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 6/05/2008 1200 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 9/05/2008 8000 4.300,00 8.600,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 13/05/2008 1000 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 16/05/2008 1400 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 20/05/2008 5300 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 23/05/2008 1800 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 27/05/2008 4200 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 30/05/2008 2600 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 3/06/2008 2400 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 6/06/2008 3700 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 10/06/2008 2000 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 13/06/2008 3600 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 17/06/2008 2400 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 20/06/2008 3000 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 24/06/2008 900 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 27/06/2008 900 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 30/06/2008 18400 4.300,00 17.200,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 31/07/2008 25900 4.300,00 25.800,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 31/08/2008 18100 4.300,00 17.200,00



Regards,
Peter

Amy Blankenship said:
Hardhit said:
Hello Amy,

The SQL is :

SELECT Query1.PoNr, Query1.SupplName, Query1.PartNr, Query1.Date,
OrderQtyCalc([PartNr],[SumOfSumOfOrderQty],[PackQty]) AS OrderQty
FROM Query1
WHERE (((OrderQtyCalc([PartNr],[SumOfSumOfOrderQty],[PackQty]))>0))
ORDER BY Query1.Date;

This query is based on another query which joins the Supplier table, The
parts Table, The POHeader table, The Orders Table and the BOM table.
In the query used above I select the PoNr and PackQty from the PO table,
the PartNr from the Parts Table, the Date and the OderQty from the
Customer Order table this is all attached to the BOM table in which I then
calculate the OrderQty based on the the number of times a part is used in
an assembly which is in the BOM table. This all results in a query which
has the following info.
Click to expand...

The problem is that your WHERE clause also uses your function, which makes
it impossible to use a "ranking" subquery to determine if you are on your
first or last record.

Let me try to state, in words, what I see your logic doing, and let's see if
we can come up with a way to do it with just one or more queries.

On each row (ordered by date)
-if this is the same part number as the previous row
-look at how much we have
-check to see if subtracting the quantity of the order results in a
negative number
-yes
-divide the amount we're short by the pack quantity,
multiply by .5
-multiply that again by the pack quantity, this is our
result
-no
reset all variables
return 0

-not the same part number
-reset variables
-perform above steps from -look at how much...

It looks to me like you've been very lucky, since you're not sorting by part
number. Your part numbers may not always be contiguous, which I would
expect to throw your numbers off big time. It also looks to me that the
only time you will _not_ have a quantity to order is if there is an order
quantity of zero.

I have some ideas of where to take this, but I don't want to invest too much
time into this until I can see what the end goal is here, not the particular
implementation that you've chosen to try.

-Amy
Click to expand...
 
A

Amy Blankenship

Is there a hard requirement to get the number you need to order line by line, or would the total do by part number?
Hello Amy,

The problem with the partnumber not being sorted I discovered yesterday when I wanted to test the results of the function when running it trhough all the partnumbers to order. I didn't have this issue before since I was only testing with 1 partnumber.
However I put a sort on the partnumber and this resolved that issue.

What I want to do is to check if I have enough parts to build my next demand (checking the negative value) if the value is positive then I have enough parts and I don't need to order the parts for that customer order. If the value is negative then I determine the number of boxes to order by deviding the negaive result by the packsize so that when I do the order I always order quantity's based on the box packsize.

Also I'm not multiplying by 0.5 but I'm adding 0.5 to the result of the negative number devided by the packsize this to make sure that my box quantity is rounded upward.

dBoxes = Round((-dCalc / dPackSize) + 0.5, 0) 'Make sure that the number of boxes is rounded upward

This is the result that the query is giving which is correct.

PoNr SupplName PartNr DelivDate SumOfOrderQty PackQty OrderQty
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 1/01/2001 14580 4.300,00 17.200,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 25/04/2008 2300 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 29/04/2008 900 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 5/05/2008 3600 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 6/05/2008 1200 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 9/05/2008 8000 4.300,00 8.600,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 13/05/2008 1000 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 16/05/2008 1400 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 20/05/2008 5300 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 23/05/2008 1800 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 27/05/2008 4200 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 30/05/2008 2600 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 3/06/2008 2400 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 6/06/2008 3700 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 10/06/2008 2000 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 13/06/2008 3600 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 17/06/2008 2400 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 20/06/2008 3000 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 24/06/2008 900 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 27/06/2008 900 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 30/06/2008 18400 4.300,00 17.200,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 31/07/2008 25900 4.300,00 25.800,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 31/08/2008 18100 4.300,00 17.200,00



Regards,
Peter

Amy Blankenship said:
Hardhit said:
Hello Amy,

The SQL is :

SELECT Query1.PoNr, Query1.SupplName, Query1.PartNr, Query1.Date,
OrderQtyCalc([PartNr],[SumOfSumOfOrderQty],[PackQty]) AS OrderQty
FROM Query1
WHERE (((OrderQtyCalc([PartNr],[SumOfSumOfOrderQty],[PackQty]))>0))
ORDER BY Query1.Date;

This query is based on another query which joins the Supplier table, The
parts Table, The POHeader table, The Orders Table and the BOM table.
In the query used above I select the PoNr and PackQty from the PO table,
the PartNr from the Parts Table, the Date and the OderQty from the
Customer Order table this is all attached to the BOM table in which I then
calculate the OrderQty based on the the number of times a part is used in
an assembly which is in the BOM table. This all results in a query which
has the following info.
Click to expand...

The problem is that your WHERE clause also uses your function, which makes
it impossible to use a "ranking" subquery to determine if you are on your
first or last record.

Let me try to state, in words, what I see your logic doing, and let's see if
we can come up with a way to do it with just one or more queries.

On each row (ordered by date)
-if this is the same part number as the previous row
-look at how much we have
-check to see if subtracting the quantity of the order results in a
negative number
-yes
-divide the amount we're short by the pack quantity,
multiply by .5
-multiply that again by the pack quantity, this is our
result
-no
reset all variables
return 0

-not the same part number
-reset variables
-perform above steps from -look at how much...

It looks to me like you've been very lucky, since you're not sorting by part
number. Your part numbers may not always be contiguous, which I would
expect to throw your numbers off big time. It also looks to me that the
only time you will _not_ have a quantity to order is if there is an order
quantity of zero.

I have some ideas of where to take this, but I don't want to invest too much
time into this until I can see what the end goal is here, not the particular
implementation that you've chosen to try.

-Amy
Click to expand...
 
H

Hardhit

Hello Amy,

I need it by line as this is for an ordering database so that a supplier can get an overview of what he needs to deliver on a certain data.

Regards,
Is there a hard requirement to get the number you need to order line by line, or would the total do by part number?
Hello Amy,

The problem with the partnumber not being sorted I discovered yesterday when I wanted to test the results of the function when running it trhough all the partnumbers to order. I didn't have this issue before since I was only testing with 1 partnumber.
However I put a sort on the partnumber and this resolved that issue.

What I want to do is to check if I have enough parts to build my next demand (checking the negative value) if the value is positive then I have enough parts and I don't need to order the parts for that customer order. If the value is negative then I determine the number of boxes to order by deviding the negaive result by the packsize so that when I do the order I always order quantity's based on the box packsize.

Also I'm not multiplying by 0.5 but I'm adding 0.5 to the result of the negative number devided by the packsize this to make sure that my box quantity is rounded upward.

dBoxes = Round((-dCalc / dPackSize) + 0.5, 0) 'Make sure that the number of boxes is rounded upward

This is the result that the query is giving which is correct.

PoNr SupplName PartNr DelivDate SumOfOrderQty PackQty OrderQty
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 1/01/2001 14580 4.300,00 17.200,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 25/04/2008 2300 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 29/04/2008 900 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 5/05/2008 3600 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 6/05/2008 1200 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 9/05/2008 8000 4.300,00 8.600,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 13/05/2008 1000 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 16/05/2008 1400 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 20/05/2008 5300 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 23/05/2008 1800 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 27/05/2008 4200 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 30/05/2008 2600 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 3/06/2008 2400 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 6/06/2008 3700 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 10/06/2008 2000 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 13/06/2008 3600 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 17/06/2008 2400 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 20/06/2008 3000 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 24/06/2008 900 4.300,00 4.300,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 27/06/2008 900 4.300,00 0,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 30/06/2008 18400 4.300,00 17.200,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 31/07/2008 25900 4.300,00 25.800,00
3 ADVANCED LABEL TECHNOLOGY 24.01.00.15 31/08/2008 18100 4.300,00 17.200,00



Regards,
Peter

Amy Blankenship said:
Hardhit said:
Hello Amy,

The SQL is :

SELECT Query1.PoNr, Query1.SupplName, Query1.PartNr, Query1.Date,
OrderQtyCalc([PartNr],[SumOfSumOfOrderQty],[PackQty]) AS OrderQty
FROM Query1
WHERE (((OrderQtyCalc([PartNr],[SumOfSumOfOrderQty],[PackQty]))>0))
ORDER BY Query1.Date;

This query is based on another query which joins the Supplier table, The
parts Table, The POHeader table, The Orders Table and the BOM table.
In the query used above I select the PoNr and PackQty from the PO table,
the PartNr from the Parts Table, the Date and the OderQty from the
Customer Order table this is all attached to the BOM table in which I then
calculate the OrderQty based on the the number of times a part is used in
an assembly which is in the BOM table. This all results in a query which
has the following info.
Click to expand...

The problem is that your WHERE clause also uses your function, which makes
it impossible to use a "ranking" subquery to determine if you are on your
first or last record.

Let me try to state, in words, what I see your logic doing, and let's see if
we can come up with a way to do it with just one or more queries.

On each row (ordered by date)
-if this is the same part number as the previous row
-look at how much we have
-check to see if subtracting the quantity of the order results in a
negative number
-yes
-divide the amount we're short by the pack quantity,
multiply by .5
-multiply that again by the pack quantity, this is our
result
-no
reset all variables
return 0

-not the same part number
-reset variables
-perform above steps from -look at how much...

It looks to me like you've been very lucky, since you're not sorting by part
number. Your part numbers may not always be contiguous, which I would
expect to throw your numbers off big time. It also looks to me that the
only time you will _not_ have a quantity to order is if there is an order
quantity of zero.

I have some ideas of where to take this, but I don't want to invest too much
time into this until I can see what the end goal is here, not the particular
implementation that you've chosen to try.

-Amy
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Order Query 3
Access Field won't show as currency in the form, shows just a number (but works fine in the query) 1
Strange problem using VB Code in Query 3
Crosstab query totals 3
Delete query using criteria from another query 1
Combining Fields in a Query into Two Fields 3
Multiselect Listbox Query Code 2
FUNCTION PREDICTING EVEN/ODD COUNT IN QUERY 1

Top