Hi David;
I appreciate your efforts to clarify the dialog. As always, speaking
precisely is vitally important to these endeavors.
> I have very rarely raised issue
> because I did not want to appear to be too disruptive.
With all due respect, this is actually one of the post positive posts
as a
Oh dear: this is quite long. Sorry, but I had a cup of tea and a think,
and decided it is appropriate as is.
On Fri, 2007-04-27 at 10:22 -0700, Joshua D. Drake wrote:
> ... or I beating
> someone into doing it right through team collaboration and positive
> reinforcement (2x4, hose, or weed pull
Chris Travers wrote:
> Hi David;
>
> The model was a vague one with only minimal items shown for
> illustration (hence the reference that the table model could be far
> more complex than mentioned).
>
> Most of the database design work is being done by Josh Drake, and he
> is an expert in such th
Original Message
Subject:Re: [Fwd: [Ledger-smb-devel] Thoughts on payment handling in
1.4.x]
Date: Fri, 27 Apr 2007 06:49:56 -0700
From: David Kawasaki <[EMAIL PROTECTED]>
To: Joshua Drake <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
If I understand
On 4/27/07, Gerald Chudyk <[EMAIL PROTECTED]> wrote:
> On 4/27/07, John Hasler <[EMAIL PROTECTED]> wrote:
> > Ed W writes:
> > > One area though that I think is likely to drop out is that sales orders,
> > > sales invoices and sales quotes are all special cases of the same object.
> >
> > Invoices
On 4/26/07, David Tangye <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-04-26 at 19:36 -0700, Chris Travers wrote:
> > On 4/26/07, Gerald Chudyk <[EMAIL PROTECTED]> wrote:
> >
> > > Are you planning total integration between accounting modules? I
> > > designed a gl like this once. The issues with ar an
On 4/27/07, John Hasler <[EMAIL PROTECTED]> wrote:
> Ed W writes:
> > One area though that I think is likely to drop out is that sales orders,
> > sales invoices and sales quotes are all special cases of the same object.
>
> Invoices are accounting transactions. Sales orders and quotes are not.
>
On 4/27/07, John Hasler <[EMAIL PROTECTED]> wrote:
> Ed W writes:
> > One area though that I think is likely to drop out is that sales orders,
> > sales invoices and sales quotes are all special cases of the same object.
>
> Invoices are accounting transactions. Sales orders and quotes are not.
I
Ed W writes:
> One area though that I think is likely to drop out is that sales orders,
> sales invoices and sales quotes are all special cases of the same object.
Invoices are accounting transactions. Sales orders and quotes are not.
--
John Hasler
[EMAIL PROTECTED]
Elmwood, WI USA
--
On 4/27/07, Ed W <[EMAIL PROTECTED]> wrote:
> Hi
>
> Can I respectfully suggest that you missed the point that David was making?
>
> Sybase wrote some great DB design books that cover this stuff really
> well and no doubt there are other books. But basically:
In general, the process is similar
On 4/26/07, John Hasler <[EMAIL PROTECTED]> wrote:
> Gerald writes:
> > Of course changing a transaction in this environment will become
> > impossible, making auditors very happy and end-users looking for ways
> > around the system.
>
> It is quite possible to create a reversing entry and mark it
Hi
> Most of the database design work is being done by Josh Drake, and he
> is an expert in such things and if he doesn't do it, I am sure he will
> provide some strong feedback on the data model. One of our major
> tasks is making the database design follow the relational model
> properly. This
Hi
> I have some ideas about preventing duplicate submissions but nothing
> definite yet.
>
I think you have to just chuck the session ID somewhere on the form and
pass that around. There is a rails plugin called something like
ActionFlow which looks like a start at this kind of structure (
13 matches
Mail list logo
