Gerald,

I’m not certain about this so you’ll have to experiment.

Scheduled transactions (‘SX’ for short) can use variables and formulas, at 
least in the amount fields. (the part I’m not sure about is the NUM field)

Enter checknum*1 for example. When the transaction fires, it should prompt you 
to enter the check number. (By using the “*1” you aren’t changing the number 
from your entry. You could optionally use ‘checknum+1’ but you’d have to enter 
the previous number for this to work. Of course ‘checknum’ is a variable name 
of your choice.)

Unfortunately, I don’t know of anyway to get a SX to feed off info from other 
transactions, in your case, previous check numbers. So this is probably not 
very useful other than to force an entry and possibly avoid duplicates. You 
could otherwise leave the field blank and add it when reviewing the transaction.

It is highly likely however, that the NUM field can’t take formulas. I haven’t 
tested this.

Regards,
Adrien

> I am running GNUCash 2.6.20 on a Linux PC.  I have set up a scheduled
> transaction to enter my church contribution into my checking account
> every sunday.
> My problem is I cannot get the scheduled transaction to enter the next
> check number and have to go into the program and enter the number
> manualy.  That is
> not to much of a problem except that the next time I need to enter a
> check the same number I entered for the contribution comes up and I
> have to manualy move
> up one number to keep from having duplicate check numbers in the
> register.
> Any and all help will be appriciated.
> 
> Gerald Ellis
> Retired

_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to