Peter,
Agreed. You could allow users to set a session date (in a manner
similar those we have discussed in prior posts) for the entry of
transactions, yet still have system-wide immutable cutoffs and date
restrictions (i.e. once the books have been closed for a period,
transactions canno
(i.e. session date) at login.
... just more fuel for discussion,
Roy
On 15-Apr-2007, at 00:59, David Tangye wrote:
> On Fri, 2007-04-13 at 07:39 -0300, Roy Nicholl wrote:
>> One of the commercial accounting packages I used years ago (simply/
>> accpac?) would prompt you to set th
Setting the "session date" to something other than the current system
date just means that it will be the value pre-entered in the date
field when a new transaction is initiated. Ideally the presence of
an audit trail mechanism internal to the system would make possible
the ability recor
Not necessarily...
One of the commercial accounting packages I used years ago (simply/
accpac?) would prompt you to set the "session date" when you ran it/
logged on. The offered default was the current system date (simply
hit return and it was yours). This allowed you to change the date
That would be handy ... but better make certain it checks (at the
time it is set, and again before it runs) that the backup process
actually has permission to create a file in the target location ...
cause, I can just see folks putting in a path to which their LMB/Web
user cannot write. ;)
I too have re-posted 'amended' invoices (when on Gnu Cash, I just
would not have 'posted' the invoice - which was (and IMHO should
always be) autonomous from 'saving' the invoice).
If my invoice was just for services, I noticed no ill effects ...
however, if the invoice included products/as
by my poor typing skills.
... all for the want of a good editor :)
Roy
On 18-Mar-2007, at 17:49, Roy Nicholl wrote:
>
>
> Separate bank accounts are necessary for departments, it just happens
> to be the way thing
put in an entry if one
does not exist.
Roy
On 18-Mar-2007, at 17:18, Chris Travers wrote:
> Hi Roy,
> Thoughts in-line.
>
> On 3/18/07, Roy Nicholl <[EMAIL PROTECTED]> wrote:
>> Chris,
>>
>> That is one of the features of GnuCash I miss after transitioning
submit an expense to the club.)
>
> Anyways, it is good to meet you and I think that we should sit down
> and start talking about how we want to structure the case study. I
> don't know how well you know anyone here but they seem like a nice
> bunch, so let's get some di
Chris,
Not even that formal ... a draft is just something that has not been
posted ... i.e. I was working on the invoice, when the phone rang so
I saved the partial to complete later rather than starting over from
scratch afterwards. As in my previous posting, the way this is just
assume
Chris,
That is one of the features of GnuCash I miss after transitioning to
SQL-Ledger / LedgerSMB. In GnuCash, you can edit and save a
transaction without posting it ... i you attempt to edit a posted
transaction, you are warned that it is posted and, in the case of an
invoice, are given
ways, it is good to meet you and I think that we should sit down
>> and start talking about how we want to structure the case study. I
>> don't know how well you know anyone here but they seem like a nice
>> bunch, so let's get some direction from the core developers abou
Geoff ... my apology for getting your name incorrect ... have no idea
how I got Greg in my mind.
On 17-Mar-2007, at 17:33, Roy Nicholl wrote:
> Greg,
> I have been using SQL-Ledger (transitioning to LedgerSMB) to
Greg,
I have been using SQL-Ledger (transitioning to LedgerSMB) to look
after the books of a local running club + it's two major races (set
up as separate departments), over the past several years.
Similar to your programme of ski lessons, we offer an annual slate
of running clinics. We a
14 matches
Mail list logo
