Re: Query corresponding to date range.
- From: maella <maella@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 12 Oct 2008 15:17:00 -0700
Hi, don't worry, advices always are wellcome for me.
I'm willing to do all you say me. I solved the problem whe the range of
dates are two weeks creating a compound code (number) like 20081011000 where
the first four digits are the year, the following two are the month, the f.
one are the fortnight (1 or 2) and the last four digits are the variety code.
That gets I can calculate the amount depending on the prices, corresponding
to two weeks. Now, I'll include another fruits with the prices changing every
3 or 4 days, and that won't work, so I'll look forward your answer.
I've thought this data base for the farmers, but in each home can be several
ones (for example the man and his wife or their children).
When a farmer makes an entry in the wharehouse (well, after passing the
fruit in a selection machine), a receipt is given by the cooperative. It
includes:
Entry code: numerical, wharehouse code (to me only information function)
Date: date, entry date
User: number, farmer name. I have a combo showing the variety name (string)
but saving the userId (number)
Variety: number, fruit variety. I have a combo showing the variety name
(string)
but saving the varietyId (number)
16: number, weight of the fruit with 16 caliber.
18: number, weight of the fruit with 18 caliber.
20: number, weight of the fruit with 20 caliber.
.............
juice: number, weight of the fruit with "juice" caliber (damaged)
****************************************************
There are 12 calibers in all. My entry table has all this fields (16 in all).
Then I've got another table with the prices with the following fields:
variety: number, number, fruit variety. I have a combo showing the variety
name
(string) but saving the varietyId (number). Each variety has
different prices
in each caliber.
startdate: date, the first date valid for these prices
enddate: date, the last date valid for these prices so these are valid in
the date
date range.
price16: currency, price of each kg of fruit with 16 caliber
price18: currency, price of each kg of fruit with 18 caliber
price20: currency, price of each kg of fruit with 18 caliber
.................
pricejuice: corrency, price of each kg of fruit with "juice" caliber
*******************************************************
I have all these fields in my prices table too, 16 if I add an Id.
I hope I've explained well.
Thanks for your attention
"Lord Kelvan" wrote:
well i think your table structure is completly wrong no offence.
databasing isnt something you can learn over night
what are the numbers in your table
i think you are going to have to rebuild your table so that it will
work for what you want to do
i can help you by telling you the different tables and where the
fields go and how they work
for me to do this i need you to list all your field and a description
of each field ie what it stores and also the datatype of each field ie
number text etc and ill try to help you build a propper DB
Regards
Kelvan
- Follow-Ups:
- Re: Query corresponding to date range.
- From: Lord Kelvan
- Re: Query corresponding to date range.
- References:
- Query corresponding to date range.
- From: maella
- Re: Query corresponding to date range.
- From: Lord Kelvan
- Re: Query corresponding to date range.
- From: maella
- Re: Query corresponding to date range.
- From: Lord Kelvan
- Query corresponding to date range.
- Prev by Date: Re: Query in crosstab won't reference field on form
- Next by Date: Re: Query in crosstab won't reference field on form
- Previous by thread: Re: Query corresponding to date range.
- Next by thread: Re: Query corresponding to date range.
- Index(es):
Relevant Pages
|
