COMPGROUPS.NET | Search | Post Question | Groups | Stream | About | Register

### Date Due Calc

• Follow

```I am trying to write a solution for renting lockers at a club. By modifying
the video rental solution from the FMP Bible.

Doing a google search I came up with Date Due Calc +Date(Month(Date of
Occupancy) +2,0,Year(Date of Occupancy))

Here's what I want to do next, if the fee is \$15 per month and customer
wants to pay \$15 or \$30 or \$45 How do I return the applicable  due date?

Thanks,
Michael
--

```
 0

```Simplify simplify simplify.

In a calc field called "date due": case(amt paid="15",date(day(today)+30,amt
paid = "30",date(day(today)+60 . . .)

Try this instead of increasing the month so that you can calculate a part
month if you need to (i.e. if someone pays you \$7.50 you can add that to the
case function and set the due date 15 days later).

"The Wolf" <elvispmpsd@earthlink.net> wrote in message
> I am trying to write a solution for renting lockers at a club. By
modifying
> the video rental solution from the FMP Bible.
>
> Doing a google search I came up with Date Due Calc +Date(Month(Date of
> Occupancy) +2,0,Year(Date of Occupancy))
>
> Here's what I want to do next, if the fee is \$15 per month and customer
> wants to pay \$15 or \$30 or \$45 How do I return the applicable  due date?
>
> Thanks,
> Michael
> --
>

```
 0

```On 10/4/03 12:34 PM, in article
C7zfb.13508\$ko%.2838@news04.bloor.is.net.cable.rogers.com, "Mimi"
<essay_help@rogers.com> opined:

I like your approach, thanks! I am getting error at end of calc "too few
separators"

What am I doing wrong?

case(Locker Fee="15",date(day(today)+30,Locker Fee =
"30",date(day(today)+60)

> Simplify simplify simplify.
>
> In a calc field called "date due": case(amt paid="15",date(day(today)+30,amt
> paid = "30",date(day(today)+60 . . .)
>
> Try this instead of increasing the month so that you can calculate a part
> month if you need to (i.e. if someone pays you \$7.50 you can add that to the
> case function and set the due date 15 days later).
>
>
>
> "The Wolf" <elvispmpsd@earthlink.net> wrote in message
>> I am trying to write a solution for renting lockers at a club. By
> modifying
>> the video rental solution from the FMP Bible.
>>
>> Doing a google search I came up with Date Due Calc +Date(Month(Date of
>> Occupancy) +2,0,Year(Date of Occupancy))
>>
>> Here's what I want to do next, if the fee is \$15 per month and customer
>> wants to pay \$15 or \$30 or \$45 How do I return the applicable  due date?
>>
>> Thanks,
>> Michael
>> --
>>
>
>

--
===================================================================
"When a broad table is to be made, and the edges of planks do not fit, the
artist takes a little from both, and makes a good joint.  In like manner
here, both sides must part with some of their demands," Benjamin Franklin
(1706-1790)
===================================================================

```
 0

```In reply to BBA431C2.3E8B7%elvispmpsd@earthlink.net on 10/4/03 8:14 AM by

Try this one:

Case(Paid Amount = "\$15.00", Date1 + 30, Paid Amount = "\$30.00", Date1 + 60,
Paid Amount = "\$45.00", Date1 + 90)

HTH

Lee
> On 10/4/03 12:34 PM, in article
> C7zfb.13508\$ko%.2838@news04.bloor.is.net.cable.rogers.com, "Mimi"
> <essay_help@rogers.com> opined:
>
>
> I like your approach, thanks! I am getting error at end of calc "too few
> separators"
>
> What am I doing wrong?
>
>
>
> case(Locker Fee="15",date(day(today)+30,Locker Fee =
> "30",date(day(today)+60)
>
>> Simplify simplify simplify.
>>
>> In a calc field called "date due": case(amt paid="15",date(day(today)+30,amt
>> paid = "30",date(day(today)+60 . . .)
>>
>> Try this instead of increasing the month so that you can calculate a part
>> month if you need to (i.e. if someone pays you \$7.50 you can add that to the
>> case function and set the due date 15 days later).
>>
>>
>>
>> "The Wolf" <elvispmpsd@earthlink.net> wrote in message
>>> I am trying to write a solution for renting lockers at a club. By
>> modifying
>>> the video rental solution from the FMP Bible.
>>>
>>> Doing a google search I came up with Date Due Calc +Date(Month(Date of
>>> Occupancy) +2,0,Year(Date of Occupancy))
>>>
>>> Here's what I want to do next, if the fee is \$15 per month and customer
>>> wants to pay \$15 or \$30 or \$45 How do I return the applicable  due date?
>>>
>>> Thanks,
>>> Michael
>>> --
>>>
>>
>>

```
 0

```Note the following:

1. an extra closing parenthesis after each date -- it should read
(day(today)) --  because you have nested functions.
2. a default option at the end of the function (a comma and a set of double
quotation  marks (,"")

> I like your approach, thanks! I am getting error at end of calc "too few
> separators"
>
> What am I doing wrong?
>
>
>
> case(Locker Fee="15",date(day(today)+30,Locker Fee =
> "30",date(day(today)+60)
>
> > Simplify simplify simplify.
> >
> > In a calc field called "date due": case(amt
paid="15",date(day(today)+30,amt
> > paid = "30",date(day(today)+60 . . .)
> >
> > Try this instead of increasing the month so that you can calculate a
part
> > month if you need to (i.e. if someone pays you \$7.50 you can add that to
the
> > case function and set the due date 15 days later).
> >
> >
> >
> > "The Wolf" <elvispmpsd@earthlink.net> wrote in message
> >> I am trying to write a solution for renting lockers at a club. By
> > modifying
> >> the video rental solution from the FMP Bible.
> >>
> >> Doing a google search I came up with Date Due Calc +Date(Month(Date of
> >> Occupancy) +2,0,Year(Date of Occupancy))
> >>
> >> Here's what I want to do next, if the fee is \$15 per month and customer
> >> wants to pay \$15 or \$30 or \$45 How do I return the applicable  due
date?
> >>
> >> Thanks,
> >> Michael
> >> --
> >>
> >
> >
>
> --
> ===================================================================
> "When a broad table is to be made, and the edges of planks do not fit, the
> artist takes a little from both, and makes a good joint.  In like manner
> here, both sides must part with some of their demands," Benjamin Franklin
> (1706-1790)
> ===================================================================
>

```
 0

```Mimi wrote:
>
> Simplify simplify simplify.
>
> In a calc field called "date due": case(amt paid="15",date(day(today)+30,amt
> paid = "30",date(day(today)+60 . . .)
>
> Try this instead of increasing the month so that you can calculate a part
> month if you need to (i.e. if someone pays you \$7.50 you can add that to the
> case function and set the due date 15 days later).
>
> "The Wolf" <elvispmpsd@earthlink.net> wrote in message
> > I am trying to write a solution for renting lockers at a club. By
> modifying
> > the video rental solution from the FMP Bible.
> >
> > Doing a google search I came up with Date Due Calc +Date(Month(Date of
> > Occupancy) +2,0,Year(Date of Occupancy))
> >
> > Here's what I want to do next, if the fee is \$15 per month and customer
> > wants to pay \$15 or \$30 or \$45 How do I return the applicable  due date?
> >
> > Thanks,
> > Michael
> > --
> >

Or, alternatively:

Date due = date(day(today)+ 30*int(amt paid/15)

That makes it easy to change the formula if you change the monthly rent,
etc. I also makes it easy for a person to pay well in advance.

Bill
--
Return address intentionally altered to avoid spam.
```
 0

```In reply to 3F7F8BD4.B22650F1@invalid.invalid on 10/4/03 8:11 PM by B
Collins bbcollins@invalid.invalid:

Hi Bill,

Nice calculation, but it had an error that would not let me close the
Calculation box. I modified it slightly it works great.

DatePaid+30*Int(Locker Fee/15)

DatePaid is the date that the locker fees are paid on. I would stay away
from the Today function as it doesn't update daily unless you close your
program. It is better to use the Status(CurrentDate) instead.

BTW, wouldn't the Due Date advance each day using "Today" or
Status(CurrentDate) in this way. (i.e. isn't 30 days from today going to be
30 days from tomorrow when tomorrow comes?) Or is it too late and my brain
stop functioning?

Lee

> Mimi wrote:
>>
>> Simplify simplify simplify.
>>
>> In a calc field called "date due": case(amt paid="15",date(day(today)+30,amt
>> paid = "30",date(day(today)+60 . . .)
>>
>> Try this instead of increasing the month so that you can calculate a part
>> month if you need to (i.e. if someone pays you \$7.50 you can add that to the
>> case function and set the due date 15 days later).
>>
>> "The Wolf" <elvispmpsd@earthlink.net> wrote in message
>>> I am trying to write a solution for renting lockers at a club. By
>> modifying
>>> the video rental solution from the FMP Bible.
>>>
>>> Doing a google search I came up with Date Due Calc +Date(Month(Date of
>>> Occupancy) +2,0,Year(Date of Occupancy))
>>>
>>> Here's what I want to do next, if the fee is \$15 per month and customer
>>> wants to pay \$15 or \$30 or \$45 How do I return the applicable  due date?
>>>
>>> Thanks,
>>> Michael
>>> --
>>>
>
> Or, alternatively:
>
> Date due = date(day(today)+ 30*int(amt paid/15)
>
> That makes it easy to change the formula if you change the monthly rent,
> etc. I also makes it easy for a person to pay well in advance.
>
> Bill

```
 0

```On 10/5/03 5:18 AM, in article BBA4F7C8.2E953%lee@pacific.net, "Lee Smith"
<lee@pacific.net> opined:

Thanks everyone for all the great advice!

So as not to overly Rube Goldberg this thing I am trying to only have two
related files.

Customers
Payments

What is the best way to handle a transaction, i.e. rent payment, a repeating
field in one record related by locker number? Or a separate record related
by field locker number.

I am trying to have portals in customers to show each payment and whether or
not they are delinquent.

One small detail I forgot to mention. There are two different size lockers,
with different fees.

> In reply to 3F7F8BD4.B22650F1@invalid.invalid on 10/4/03 8:11 PM by B
> Collins bbcollins@invalid.invalid:
>
> Hi Bill,
>
> Nice calculation, but it had an error that would not let me close the
> Calculation box. I modified it slightly it works great.
>
> DatePaid+30*Int(Locker Fee/15)
>
> DatePaid is the date that the locker fees are paid on. I would stay away
> from the Today function as it doesn't update daily unless you close your
> program. It is better to use the Status(CurrentDate) instead.
>
> BTW, wouldn't the Due Date advance each day using "Today" or
> Status(CurrentDate) in this way. (i.e. isn't 30 days from today going to be
> 30 days from tomorrow when tomorrow comes?) Or is it too late and my brain
> stop functioning?
>
> Lee
>
>
>> Mimi wrote:
>>>
>>> Simplify simplify simplify.
>>>
>>> In a calc field called "date due": case(amt paid="15",date(day(today)+30,amt
>>> paid = "30",date(day(today)+60 . . .)
>>>
>>> Try this instead of increasing the month so that you can calculate a part
>>> month if you need to (i.e. if someone pays you \$7.50 you can add that to the
>>> case function and set the due date 15 days later).
>>>
>>> "The Wolf" <elvispmpsd@earthlink.net> wrote in message
>>>> I am trying to write a solution for renting lockers at a club. By
>>> modifying
>>>> the video rental solution from the FMP Bible.
>>>>
>>>> Doing a google search I came up with Date Due Calc +Date(Month(Date of
>>>> Occupancy) +2,0,Year(Date of Occupancy))
>>>>
>>>> Here's what I want to do next, if the fee is \$15 per month and customer
>>>> wants to pay \$15 or \$30 or \$45 How do I return the applicable  due date?
>>>>
>>>> Thanks,
>>>> Michael
>>>> --
>>>>
>>
>> Or, alternatively:
>>
>> Date due = date(day(today)+ 30*int(amt paid/15)
>>
>> That makes it easy to change the formula if you change the monthly rent,
>> etc. I also makes it easy for a person to pay well in advance.
>>
>> Bill
>

--
===================================================================
"When a broad table is to be made, and the edges of planks do not fit, the
artist takes a little from both, and makes a good joint.  In like manner
here, both sides must part with some of their demands," Benjamin Franklin
(1706-1790)
===================================================================

```
 0

```Lee Smith wrote:
>
> In reply to 3F7F8BD4.B22650F1@invalid.invalid on 10/4/03 8:11 PM by B
> Collins bbcollins@invalid.invalid:
>
> Hi Bill,
>
> Nice calculation, but it had an error that would not let me close the
> Calculation box. I modified it slightly it works great.
>
> DatePaid+30*Int(Locker Fee/15)
>
> DatePaid is the date that the locker fees are paid on. I would stay away
> from the Today function as it doesn't update daily unless you close your
> program. It is better to use the Status(CurrentDate) instead.
>
> BTW, wouldn't the Due Date advance each day using "Today" or
> Status(CurrentDate) in this way. (i.e. isn't 30 days from today going to be
> 30 days from tomorrow when tomorrow comes?) Or is it too late and my brain
> stop functioning?
>
> Lee
>
> > Mimi wrote:
> >>
> >> Simplify simplify simplify.
> >>
> >> In a calc field called "date due": case(amt paid="15",date(day(today)+30,amt
> >> paid = "30",date(day(today)+60 . . .)
> >>
> >> Try this instead of increasing the month so that you can calculate a part
> >> month if you need to (i.e. if someone pays you \$7.50 you can add that to the
> >> case function and set the due date 15 days later).
> >>
> >> "The Wolf" <elvispmpsd@earthlink.net> wrote in message
> >>> I am trying to write a solution for renting lockers at a club. By
> >> modifying
> >>> the video rental solution from the FMP Bible.
> >>>
> >>> Doing a google search I came up with Date Due Calc +Date(Month(Date of
> >>> Occupancy) +2,0,Year(Date of Occupancy))
> >>>
> >>> Here's what I want to do next, if the fee is \$15 per month and customer
> >>> wants to pay \$15 or \$30 or \$45 How do I return the applicable  due date?
> >>>
> >>> Thanks,
> >>> Michael
> >>> --
> >>>
> >
> > Or, alternatively:
> >
> > Date due = date(day(today)+ 30*int(amt paid/15)
> >
> > That makes it easy to change the formula if you change the monthly rent,
> > etc. I also makes it easy for a person to pay well in advance.
> >
> > Bill

Good catch. You are right on all counts.

Bill
--
Return address intentionally altered to avoid spam.
```
 0

```On 10/6/03 12:01 AM, in article 3F80B0F5.9F37D4FD@invalid.invalid, "B
Collins" <bbcollins@invalid.invalid> opined:

> Lee Smith wrote:
>>
>> In reply to 3F7F8BD4.B22650F1@invalid.invalid on 10/4/03 8:11 PM by B
>> Collins bbcollins@invalid.invalid:
>>
>> Hi Bill,
>>
>> Nice calculation, but it had an error that would not let me close the
>> Calculation box. I modified it slightly it works great.
>>
>> DatePaid+30*Int(Locker Fee/15)
>>
>> DatePaid is the date that the locker fees are paid on. I would stay away
>> from the Today function as it doesn't update daily unless you close your
>> program. It is better to use the Status(CurrentDate) instead.
>>
>> BTW, wouldn't the Due Date advance each day using "Today" or
>> Status(CurrentDate) in this way. (i.e. isn't 30 days from today going to be
>> 30 days from tomorrow when tomorrow comes?) Or is it too late and my brain
>> stop functioning?
>>
>> Lee
>>
>>> Mimi wrote:
>>>>
>>>> Simplify simplify simplify.
>>>>
>>>> In a calc field called "date due": case(amt
>>>> paid="15",date(day(today)+30,amt
>>>> paid = "30",date(day(today)+60 . . .)
>>>>
>>>> Try this instead of increasing the month so that you can calculate a part
>>>> month if you need to (i.e. if someone pays you \$7.50 you can add that to
>>>> the
>>>> case function and set the due date 15 days later).
>>>>
>>>> "The Wolf" <elvispmpsd@earthlink.net> wrote in message
>>>>> I am trying to write a solution for renting lockers at a club. By
>>>> modifying
>>>>> the video rental solution from the FMP Bible.
>>>>>
>>>>> Doing a google search I came up with Date Due Calc +Date(Month(Date of
>>>>> Occupancy) +2,0,Year(Date of Occupancy))
>>>>>
>>>>> Here's what I want to do next, if the fee is \$15 per month and customer
>>>>> wants to pay \$15 or \$30 or \$45 How do I return the applicable  due date?
>>>>>
>>>>> Thanks,
>>>>> Michael
>>>>> --
>>>>>
>>>
>>> Or, alternatively:
>>>
>>> Date due = date(day(today)+ 30*int(amt paid/15)
>>>
>>> That makes it easy to change the formula if you change the monthly rent,
>>> etc. I also makes it easy for a person to pay well in advance.
>>>
>>> Bill
>
> Good catch. You are right on all counts.
>
> Bill

This one returns the date the payment was made for me instead of the date
due. What is wrong?
--

```
 0

```In reply to BBA60856.3EA2F%elvispmpsd@earthlink.net on 10/5/03 5:42 PM by

> On 10/6/03 12:01 AM, in article 3F80B0F5.9F37D4FD@invalid.invalid, "B
> Collins" <bbcollins@invalid.invalid> opined:
>
>> Lee Smith wrote:
>>>
>>> In reply to 3F7F8BD4.B22650F1@invalid.invalid on 10/4/03 8:11 PM by B
>>> Collins bbcollins@invalid.invalid:
>>>
>>> Hi Bill,
>>>
>>> Nice calculation, but it had an error that would not let me close the
>>> Calculation box. I modified it slightly it works great.
>>>
>>> DatePaid+30*Int(Locker Fee/15)
>>>
--snip--

you need a field called "Locker Fee" (without ") and I would use a popup
menu for ease of entry with a value list like:
15.00
30.00
45.00

HTH

Lee

> This one returns the date the payment was made for me instead of the date
> due. What is wrong?

```
 0

```On 10/6/03 12:51 AM, in article BBA60A9B.2E994%lee@pacific.net, "Lee Smith"
<lee@pacific.net> opined:

Thanks, I had one from the other database "customers" I was trying to relate
to. Once I created a field in the "payment" database it worked fine.

How would you handle a transaction, i.e. rent payment, a repeating
field in one record related by locker number? Or a separate record related
by field locker number.

I am trying to have portals in customers to show each payment and whether or
not they are delinquent.

One small detail I forgot to mention. There are two different size lockers,
with different fees.

>
> --snip--
>
> you need a field called "Locker Fee" (without ") and I would use a popup
> menu for ease of entry with a value list like:
> 15.00
> 30.00
> 45.00
>
> HTH
>
> Lee
>
>> This one returns the date the payment was made for me instead of the date
>> due. What is wrong?
>

--
===================================================================
"When a broad table is to be made, and the edges of planks do not fit, the
artist takes a little from both, and makes a good joint.  In like manner
here, both sides must part with some of their demands," Benjamin Franklin
(1706-1790)
===================================================================

```
 0

```On 10/6/03 12:51 AM, in article BBA60A9B.2E994%lee@pacific.net, "Lee Smith"
<lee@pacific.net> opined:

I got the next payment due calc to work now I want to show who's delinquent

Today- Next Payment Due

This gives me the number of days delinquent is there a way it can show 0 if
the account is up to date? What is does now is give a negative number.

Thanks,
Michael
--

it works great.
>>>>
>>>> DatePaid+30*Int(Locker Fee/15)
>>>>
> --snip--
>
> you need a field called "Locker Fee" (without ") and I would use a popup
> menu for ease of entry with a value list like:
> 15.00
> 30.00
> 45.00
>
> HTH
>
> Lee
>
>> This one returns the date the payment was made for me instead of the date
>> due. What is wrong?
>

```
 0

```Days Delinquent (calculation, number) = Max (0, Status (CurrentDate) - Next
Payment Due)

"The Wolf" <elvispmpsd@earthlink.net> wrote in message
> On 10/6/03 12:51 AM, in article BBA60A9B.2E994%lee@pacific.net, "Lee
Smith"
> <lee@pacific.net> opined:
>
> I got the next payment due calc to work now I want to show who's
delinquent
>
> Today- Next Payment Due
>
> This gives me the number of days delinquent is there a way it can show 0
if
> the account is up to date? What is does now is give a negative number.
>
> Thanks,
> Michael
> --
>
>
>  it works great.
> >>>>
> >>>> DatePaid+30*Int(Locker Fee/15)
> >>>>
> > --snip--
> >
> > you need a field called "Locker Fee" (without ") and I would use a popup
> > menu for ease of entry with a value list like:
> > 15.00
> > 30.00
> > 45.00
> >
> > HTH
> >
> > Lee
> >
> >> This one returns the date the payment was made for me instead of the
date
> >> due. What is wrong?
> >
>
>

```
 0

```On 10/6/03 2:07 PM, in article vo2tojca00co2f@corp.supernews.com, "Glenn
Schwandt" <schwandtgat@aoldot.com> opined:

> Max (0, Status (CurrentDate) - Next
> Payment Due)

OK, that works fine THANK YOU!

Could I please go to the well once more?

There are two different size lockers that rent at different rates.

All the calcs are set up for the smaller one. How do I work a customer who
rents the bigger one?

I have the payments related by locker number. Can the relationship plug in
the rate for that locker in the payment data base?

If Joe Public rents locker #1 he pays \$10
If Joe Public rents locker #2 he pays \$20
--
===================================================================
"When a broad table is to be made, and the edges of planks do not fit, the
artist takes a little from both, and makes a good joint.  In like manner
here, both sides must part with some of their demands," Benjamin Franklin
(1706-1790)
===================================================================

```
 0

```"The Wolf" <elvispmpsd@earthlink.net> wrote in message
> On 10/6/03 2:07 PM, in article vo2tojca00co2f@corp.supernews.com, "Glenn
> Schwandt" <schwandtgat@aoldot.com> opined:
>
> > Max (0, Status (CurrentDate) - Next
> > Payment Due)
>
> OK, that works fine THANK YOU!
>
> Could I please go to the well once more?
>
> There are two different size lockers that rent at different rates.
>
> All the calcs are set up for the smaller one. How do I work a customer who
> rents the bigger one?
>
> I have the payments related by locker number. Can the relationship plug in
> the rate for that locker in the payment data base?
>
> If Joe Public rents locker #1 he pays \$10
> If Joe Public rents locker #2 he pays \$20
> --

Sounds reasonable, but short of seeing your database structure (field
definitions, relationships, etc.), I'm not sure I can tell you exactly how
you would do it in your case.

```
 0

```On 10/6/03 7:53 PM, in article vo3i18jitifi8e@corp.supernews.com, "Glenn
Schwandt" <schwandtgat@aoldot.com> opined:

> "The Wolf" <elvispmpsd@earthlink.net> wrote in message
>> On 10/6/03 2:07 PM, in article vo2tojca00co2f@corp.supernews.com, "Glenn
>> Schwandt" <schwandtgat@aoldot.com> opined:
>>
>>> Max (0, Status (CurrentDate) - Next
>>> Payment Due)
>>
>> OK, that works fine THANK YOU!
>>
>> Could I please go to the well once more?
>>
>> There are two different size lockers that rent at different rates.
>>
>> All the calcs are set up for the smaller one. How do I work a customer who
>> rents the bigger one?
>>
>> I have the payments related by locker number. Can the relationship plug in
>> the rate for that locker in the payment data base?
>>
>> If Joe Public rents locker #1 he pays \$10
>> If Joe Public rents locker #2 he pays \$20
>> --
>
> Sounds reasonable, but short of seeing your database structure (field
> definitions, relationships, etc.), I'm not sure I can tell you exactly how
> you would do it in your case.
>
>

Database "Payments" related to database "Customers" by field "Locker Number"

There are two size lockers monthly rent is \$10 and \$15, small and large.

Thanks to everyone's help the "payment" database works fine with the \$10
lockers.

How do I record a payment for someone with the larger locker. All the calcs
are for the \$15 lockers?

--
===================================================================
"When a broad table is to be made, and the edges of planks do not fit, the
artist takes a little from both, and makes a good joint.  In like manner
here, both sides must part with some of their demands," Benjamin Franklin
(1706-1790)
===================================================================

```
 0

```"The Wolf" <elvispmpsd@earthlink.net> wrote in message
> On 10/6/03 7:53 PM, in article vo3i18jitifi8e@corp.supernews.com, "Glenn
> Schwandt" <schwandtgat@aoldot.com> opined:
>
> > "The Wolf" <elvispmpsd@earthlink.net> wrote in message
> >> On 10/6/03 2:07 PM, in article vo2tojca00co2f@corp.supernews.com,
"Glenn
> >> Schwandt" <schwandtgat@aoldot.com> opined:
> >>
> >>> Max (0, Status (CurrentDate) - Next
> >>> Payment Due)
> >>
> >> OK, that works fine THANK YOU!
> >>
> >> Could I please go to the well once more?
> >>
> >> There are two different size lockers that rent at different rates.
> >>
> >> All the calcs are set up for the smaller one. How do I work a customer
who
> >> rents the bigger one?
> >>
> >> I have the payments related by locker number. Can the relationship plug
in
> >> the rate for that locker in the payment data base?
> >>
> >> If Joe Public rents locker #1 he pays \$10
> >> If Joe Public rents locker #2 he pays \$20
> >> --
> >
> > Sounds reasonable, but short of seeing your database structure (field
> > definitions, relationships, etc.), I'm not sure I can tell you exactly
how
> > you would do it in your case.
> >
> >
>
> Database "Payments" related to database "Customers" by field "Locker
Number"
>
> There are two size lockers monthly rent is \$10 and \$15, small and large.
>
> Thanks to everyone's help the "payment" database works fine with the \$10
> lockers.
>
> How do I record a payment for someone with the larger locker. All the
calcs
> are for the \$15 lockers?
>
> --

Based on the information just provided above, I would suggest substituting
the "Locker Fee" field, via the "Locker Number" relationship, anywhere you
use a static dollar amount in your calculations.  But again, I might be able
to be more specific if you provided more detail about your solution, like
the exact calculations you currently have that aren't providing the desired
results, in which database they reside, where the variable information is
located (locker fee), etc.

```
 0

```On 10/7/03 1:48 PM, in article vo5h1ka1gefha9@corp.supernews.com, "Glenn
Schwandt" <schwandtgat@aoldot.com> opined:

> "The Wolf" <elvispmpsd@earthlink.net> wrote in message
>> On 10/6/03 7:53 PM, in article vo3i18jitifi8e@corp.supernews.com, "Glenn
>> Schwandt" <schwandtgat@aoldot.com> opined:
>>
>>> "The Wolf" <elvispmpsd@earthlink.net> wrote in message
>>>> On 10/6/03 2:07 PM, in article vo2tojca00co2f@corp.supernews.com,
> "Glenn
>>>> Schwandt" <schwandtgat@aoldot.com> opined:
>>>>
>>>>> Max (0, Status (CurrentDate) - Next
>>>>> Payment Due)
>>>>
>>>> OK, that works fine THANK YOU!
>>>>
>>>> Could I please go to the well once more?
>>>>
>>>> There are two different size lockers that rent at different rates.
>>>>
>>>> All the calcs are set up for the smaller one. How do I work a customer
> who
>>>> rents the bigger one?
>>>>
>>>> I have the payments related by locker number. Can the relationship plug
> in
>>>> the rate for that locker in the payment data base?
>>>>
>>>> If Joe Public rents locker #1 he pays \$10
>>>> If Joe Public rents locker #2 he pays \$20
>>>> --
>>>
>>> Sounds reasonable, but short of seeing your database structure (field
>>> definitions, relationships, etc.), I'm not sure I can tell you exactly
> how
>>> you would do it in your case.
>>>
>>>
>>
>> Database "Payments" related to database "Customers" by field "Locker
> Number"
>>
>> There are two size lockers monthly rent is \$10 and \$15, small and large.
>>
>> Thanks to everyone's help the "payment" database works fine with the \$10
>> lockers.
>>
>> How do I record a payment for someone with the larger locker. All the
> calcs
>> are for the \$15 lockers?
>>
>> --
>
> Based on the information just provided above, I would suggest substituting
> the "Locker Fee" field, via the "Locker Number" relationship, anywhere you
> use a static dollar amount in your calculations.  But again, I might be able
> to be more specific if you provided more detail about your solution, like
> the exact calculations you currently have that aren't providing the desired
> results, in which database they reside, where the variable information is
> located (locker fee), etc.
>
>
Could I email clones of the files so you could look at the calcs?
--
===================================================================
"When a broad table is to be made, and the edges of planks do not fit, the
artist takes a little from both, and makes a good joint.  In like manner
here, both sides must part with some of their demands," Benjamin Franklin
(1706-1790)
===================================================================

```
 0

```"The Wolf" <elvispmpsd@earthlink.net> wrote in message

> On 10/7/03 1:48 PM, in article vo5h1ka1gefha9@corp.supernews.com, "Glenn
> Schwandt" <schwandtgat@aoldot.com> opined:
>
> >
> > Based on the information just provided above, I would suggest
substituting
> > the "Locker Fee" field, via the "Locker Number" relationship, anywhere
you
> > use a static dollar amount in your calculations.  But again, I might be
able
> > to be more specific if you provided more detail about your solution,
like
> > the exact calculations you currently have that aren't providing the
desired
> > results, in which database they reside, where the variable information
is
> > located (locker fee), etc.
> >
> >
> Could I email clones of the files so you could look at the calcs?
> --

Sure, I'll take a look when I have a moment.  Just drop the "at" and "dot"

```
 0

19 Replies
165 Views

Similiar Articles:

7/25/2012 11:57:42 AM