Steve:
I believe you can do everything you want to do with either
the biweekly
or every X days options. Use biweekly for your 14-day
example.
Rob Meredith
>>> steveziel sbcglobal.net 09/12/06 09:07AM
>>>
Hi Rob,
Cool on fixing up the 1970 and the missing dates with the
semi-monthly
schedule. But this brings up something to me. If by
semi-monthly you
really mean two payments per month, on a specific date of
the month, it
is a
rather unusual payment schedule. Not that someone would not
have a use
for
it.
Examine January 2006 for instance. Pick the defaults of the
15th and
the
30th. The 15th is a Sunday, defaulting back to Friday the
13th. The
30th
is a Monday. In February the 15th is a Wednesday, and there
is no
30th. I
suppose the program would put the payment on the 1st of
March, kind of
like
trying to establish a transaction on April 31, the program
makes the
date
March 1. I'm not too concerned about what happens when
there is no
30th in
a month with this message though. Then the 15th of March
and 30th
would be
on Wednesday, and Thursday, respectively. You can see that
this gives
an
irratic payment schedule, though the date itself remains the
same.
Perhaps what the program reeally needs is payments on every
fourteenth
day,
where the user picks the day of the week. The Brits would
call this
fortnight, but Americans probably generally wouldn't know
the term.
For
instance, I get paid on Mondays, there usually are two
Mondays in a
month,
sometime three. I have a school teacher friend who is paid
every other
Tuesday. Most folks get paid every other Friday.
So if there were a box called "Every Other", or
"Every 14th", then the
next
tab area would be the days of the week, seven choices from
Sunday
through
Saturday, (or possibly more efficient and suggestive, Friday
through
Sunday), this type of every fourteenth day payment date
method would be
addressed. It would handle twice a month or three times a
month
payments as
well.
There would be no need to create a weekend action button,
"exact post"
or
Weekend before or after, as the user themselves would select
the actual
payment date. Some folks, I'm sure do get paid on
Saturdays.
Please give this some consideration. Perhaps the
semi-monthly offering
currently in the program is useful to some, but it doesn't
really solve
the
need for an every fourteenth day periodic payment schedule.
Thanks
Steve
----- Original Message -----
From: "ROB MEREDITH" <rmeredithaph.org>
To: <moneytalksfreelists.org>
Sent: Monday, September 11, 2006 11:16 AM
Subject: [moneytalks] Re: Beta: .222 acting real nasty
withsemi-monthly
recurring transactions
> Steve:
>
> You found a real bug, but it isn't quite you think.
>
> The semi monthly transaction always post as if you had
selected the
> previous week day. This is not in the manual, but it is
correct. So
that
> part is fine. This type of transaction is really only
intended for
those
> who get paid twice a month.
>
> The real bug is the absents of a post on the correct
day or a post
with
> the year as 1970. I will fix that one, and thanks for
pointing it
out.
>
> Rob Meredith
>
>>>> stevezielsbcglobal.net 09/09/06
01:51AM >>>
> Hello MT folks,
>
>
>
> I downloaded beta 1.1.0.222 on Friday, Sept. 8. It
seems with beta
.222
>
> semi-monthly recurring transactions are acting
incorrectly. In the
> examples
> below I used zero as the advanced notice date. I made a
September 8,
> 2006
> transaction recurring. That date is a Friday. I chose
the 10th and
the
> 20th
> as the semi-monthly posting dates. I then projected the
transaction
> through
> December 31, 2006. The program skipped September 10,
which is a
Sunday,
>
> posted on September 20. Correct postings occured until
December 8,
> which is
> incorrect and is also a Friday. Weekend action is not
an option in
the
>
> semi-monthly choice in the frequency box.
>
>
>
> Informationally, I erased all the postings, except for
the one with
the
> "R"
> in the status column, changed its date back to
September 8, 2006,
and
> manually used the "post next recurring"
command through December
2006.
> Got
> the same results, so that's apparently not an issue.
>
>
>
> I also selected September 8 2006 as the current date,
made it
recurring
>
> semimonthly chose the 3rd of the month and the 12th of
the month. I
> then
> chose "project recurring" and projected
through December 31, 2006.
> NOTHING
> HAPPENED. It did not project forward from September 8,
2006.
>
>
>
> I then selected to "post next recurring"
for a one-time posting. It
> projected to, get this, January 1, 1970. My register
then had two
> transactions in it. Both of them had an "R"
in the status column.
When
> I
> looked at the recurring settings for the September 8
transaction it
was
>
> turned off. I looked at the settings for the January 1,
1970
> transaction and
> it had the semi-monthly settings I had originally set
up for
September
> 8.
>
>
>
> A couple more examples: I projected on the date of
September 11,
2006,
> it
> posted September 20, October 10, and correctly until it
came to
> December 8,
> 2006, which is incorrect.
>
>
>
> You have odd behavior with the 15th and 30th chosen as
dates. You
get
> postings on the 15th and 30th at times, but also the
13th, and 29th.
> Again I
> projected through December 31, 2006.
>
>
>
> There's definnately a snake in the wood pile here.
Hopefully you can
> kill
> it.
>
>
> Steve
>
> ps Thanks for the check number fix in multiple
recurring
transactions,
> Rob.
>
> "I purr, therefore I am"
> -- Descates
> 1596-1650
>
>
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.405 / Virus Database: 268.12.2/443 -
Release Date:
9/11/2006
>
>
|