Erik Huelsmann wrote:
> That's an option of course. Do you ever look back all those years? Or do
you
> simply look back 1 or 2 years? If the latter, it might make sense to
compress
> everything from before that period into a starting balance and try to
migrate
> the transactions
On Mon, Feb 1, 2016 at 3:23 PM, Michael Richardson wrote:
> Erik Huelsmann wrote:
> > That's an option of course. Do you ever look back all those years?
> Or do you
> > simply look back 1 or 2 years? If the latter, it might make sense to
> compress
> > everything from before that per
> > You'll be going from 1.3 to 1.4, right? That's no problem. One
>> solution here
>> > would be to cut the 1.3->1.4 migration script down to the bits that
>> are just
>> > for contacts. That'd basically just seed your database with
>> customers/vendors
>> > and other contacts.
>>
Erik Huelsmann wrote:
> I'll set up a 1.4.12 instance myself and see if I can produce the
> "employee" issue there. If so, then I would expect the problem to be
> resolved by 1.4.23, because I'm not having it at the moment and I'm not
> aware of any other users of recent versions t
On Mon, Feb 1, 2016 at 8:19 PM, Michael Richardson wrote:
> Erik Huelsmann wrote:
> > I'll set up a 1.4.12 instance myself and see if I can produce the
> > "employee" issue there. If so, then I would expect the problem to be
> > resolved by 1.4.23, because I'm not having it at the mo
On Mon, Feb 1, 2016 at 8:44 PM, Erik Huelsmann wrote:
>
>
> On Mon, Feb 1, 2016 at 8:19 PM, Michael Richardson
> wrote:
>
>> Erik Huelsmann wrote:
>> > I'll set up a 1.4.12 instance myself and see if I can produce the
>> > "employee" issue there. If so, then I would expect the problem t
