> On Jun 6, 2019, at 1:21 PM, Colin Law wrote:
>
> On Thu, 6 Jun 2019 at 19:04, Adrien Monteleone
> wrote:
>>
>>
>>> On Jun 6, 2019, at 12:40 PM, David Carlson
>>> wrote:
>>>
>>> Adrien,
>>>
>>> Looking at your comments, I have two questions.
>>>
>>> 1. Does SQLite not allow pending
On Thu, 6 Jun 2019 at 19:04, Adrien Monteleone
wrote:
>
>
> > On Jun 6, 2019, at 12:40 PM, David Carlson
> > wrote:
> >
> > Adrien,
> >
> > Looking at your comments, I have two questions.
> >
> > 1. Does SQLite not allow pending edits at all? or is it after every
> > keystroke? How do you
Aha!
In File > Properties then, not Preferences.
I keep forgetting book properties even exist.
Thanks!
Regards,
Adrien
> On Jun 6, 2019, at 1:11 PM, Geert Janssens wrote:
>
> Op donderdag 6 juni 2019 19:27:37 CEST schreef David Carlson:
>> Adrien, I thought there was also an option to turn
On 6/6/2019 10:07 AM, Stephen C. Camidge wrote:
For personal use and for most businesses, this would be the appropriate method.
For larger businesses with EDP Auditors (do they still exist?) and regulations
with accountability for the how data is maintained, the transactions should be
locked.
> On Jun 6, 2019, at 12:40 PM, David Carlson
> wrote:
>
> Adrien,
>
> Looking at your comments, I have two questions.
>
> 1. Does SQLite not allow pending edits at all? or is it after every
> keystroke? How do you avoid accidental deletions?
Not sure specifically what you mean by
Adrien, I thought there was also an option to turn on or off the blue line
in the register after today's date. I cannot find that either.
David Carlson
On Thu, Jun 6, 2019 at 11:22 AM Adrien Monteleone <
adrien.montele...@lusfiber.net> wrote:
> I could have sworn there was a simple (and easily
I could have sworn there was a simple (and easily defeat-able) locking
mechanism based on number of days that had passed, but I can’t seem to find the
preference.
Perhaps I was imagining things.
Regardless, if one wants to use correcting transactions, that is certainly
still doable, and there
I think we are mostly talking about removing errors in new transactions
before they are initially committed, not removing old errors. If every
sloppy keystroke or cat--track had to stay, we would never get anything
done.
David Carlson
On Thu, Jun 6, 2019, 9:09 AM Stephen C. Camidge
wrote:
>
On 6/5/2019 3:45 PM, Stephen M. Butler wrote:
If you did that, then you didn't properly remove the other splits. You
need to go into each cell and manually remove the data, then tab out..
Then use the arrow key to move up and the split will disappear. Continue
until all the extra splits are
