Add @findex inside document to index --options cited in document
This commit is contained in:
parent
ace9629631
commit
ec6337403a
1 changed files with 79 additions and 23 deletions
|
|
@ -874,9 +874,11 @@ P 2004/06/21 02:18:02 AAPL $32.91
|
||||||
P 2004/06/21 02:18:02 AU $400.00
|
P 2004/06/21 02:18:02 AU $400.00
|
||||||
@end smallexample
|
@end smallexample
|
||||||
|
|
||||||
|
@findex --price-db FILE
|
||||||
|
@findex --market
|
||||||
Specify the price history to use with the @code{--price-db} option,
|
Specify the price history to use with the @code{--price-db} option,
|
||||||
with the @code{-V} option to report in terms of current market
|
with the @code{-V (--market)} option to report in terms of current
|
||||||
value:
|
market value:
|
||||||
|
|
||||||
@smallexample
|
@smallexample
|
||||||
$ ledger --price-db prices.db -V balance brokerage
|
$ ledger --price-db prices.db -V balance brokerage
|
||||||
|
|
@ -1172,6 +1174,7 @@ sense:
|
||||||
$ ledger bal -^Assets
|
$ ledger bal -^Assets
|
||||||
@end smallexample
|
@end smallexample
|
||||||
|
|
||||||
|
@findex --real
|
||||||
If the @code{--real} option is used, the report will be in terms of
|
If the @code{--real} option is used, the report will be in terms of
|
||||||
the real accounts:
|
the real accounts:
|
||||||
|
|
||||||
|
|
@ -1210,6 +1213,8 @@ Note how the accounts now relate only to the real accounts, and any
|
||||||
balance or registers reports will reflect this. That the transactions
|
balance or registers reports will reflect this. That the transactions
|
||||||
relate to a particular fund is kept only in the code.
|
relate to a particular fund is kept only in the code.
|
||||||
|
|
||||||
|
@findex --code-as-payee
|
||||||
|
@findex --by-payee
|
||||||
How does this become a fund report? By using the
|
How does this become a fund report? By using the
|
||||||
@code{--code-as-payee} option, you can generate a register report
|
@code{--code-as-payee} option, you can generate a register report
|
||||||
where the payee for each posting shows the code. Alone, this is
|
where the payee for each posting shows the code. Alone, this is
|
||||||
|
|
@ -1616,11 +1621,14 @@ Assets:Checking because its amount is null.
|
||||||
|
|
||||||
@node Complete control over commodity pricing, , Fixing Lot Prices, Currency and Commodities
|
@node Complete control over commodity pricing, , Fixing Lot Prices, Currency and Commodities
|
||||||
@subsection Complete control over commodity pricing
|
@subsection Complete control over commodity pricing
|
||||||
|
@findex --market
|
||||||
|
@findex --exchange
|
||||||
|
|
||||||
Ledger allows you to have very detailed control over how your
|
Ledger allows you to have very detailed control over how your
|
||||||
commodities are valued. You can fine tune the results given using the
|
commodities are valued. You can fine tune the results given using the
|
||||||
@code{--market} or @code{--exchange} options. There are now several
|
@code{--market} or @code{--exchange} options. There are now several
|
||||||
points of interception, you can specify the valuation method:
|
points of interception, you can specify the valuation method:
|
||||||
|
|
||||||
@enumerate
|
@enumerate
|
||||||
@item on a commodity itself
|
@item on a commodity itself
|
||||||
@item on a posting, via metadata (affect is largely the same as #1)
|
@item on a posting, via metadata (affect is largely the same as #1)
|
||||||
|
|
@ -1647,8 +1655,8 @@ The reference date the price should be relative.
|
||||||
|
|
||||||
@item target
|
@item target
|
||||||
A string identifying the ``target'' commodity, or the commodity the
|
A string identifying the ``target'' commodity, or the commodity the
|
||||||
returned price should be in. This argument is null if
|
returned price should be in. This argument is null if @code{--market}
|
||||||
@code{--market} was used instead of @code{--exchange}.
|
was used instead of @code{--exchange}.
|
||||||
@end table
|
@end table
|
||||||
|
|
||||||
The valuation function should return an amount. If you've written
|
The valuation function should return an amount. If you've written
|
||||||
|
|
@ -1762,6 +1770,7 @@ ledger reg -V food
|
||||||
|
|
||||||
@node Keeping it Consistent, Journal Format, Currency and Commodities, Keeping a Journal
|
@node Keeping it Consistent, Journal Format, Currency and Commodities, Keeping a Journal
|
||||||
@section Keeping it Consistent
|
@section Keeping it Consistent
|
||||||
|
@findex --strict
|
||||||
|
|
||||||
Sometimes Ledger's flexibility can lead to difficulties. Using a
|
Sometimes Ledger's flexibility can lead to difficulties. Using a
|
||||||
freeform text editor to enter transactions makes it easy to keep the
|
freeform text editor to enter transactions makes it easy to keep the
|
||||||
|
|
@ -1890,6 +1899,8 @@ Ledger.
|
||||||
|
|
||||||
@node Command Directives, , Transaction and Comments, Journal Format
|
@node Command Directives, , Transaction and Comments, Journal Format
|
||||||
@subsection Command Directives
|
@subsection Command Directives
|
||||||
|
@findex --strict
|
||||||
|
@findex --pedantic
|
||||||
|
|
||||||
@table @code
|
@table @code
|
||||||
@item beginning of line
|
@item beginning of line
|
||||||
|
|
@ -2485,6 +2496,7 @@ This transaction is identical to writing:
|
||||||
|
|
||||||
@node Auxiliary dates, Codes, Eliding amounts, Transactions
|
@node Auxiliary dates, Codes, Eliding amounts, Transactions
|
||||||
@section Auxiliary dates
|
@section Auxiliary dates
|
||||||
|
@findex --aux-date
|
||||||
|
|
||||||
You can associate a second date with a transaction by following the
|
You can associate a second date with a transaction by following the
|
||||||
primary date with an equals sign:
|
primary date with an equals sign:
|
||||||
|
|
@ -2516,6 +2528,9 @@ you a place to put those codes:
|
||||||
|
|
||||||
@node Transaction state, Transaction notes, Codes, Transactions
|
@node Transaction state, Transaction notes, Codes, Transactions
|
||||||
@section Transaction state
|
@section Transaction state
|
||||||
|
@findex --cleared
|
||||||
|
@findex --uncleared
|
||||||
|
@findex --pending
|
||||||
|
|
||||||
A transaction can have a ``state'': cleared, pending, or uncleared.
|
A transaction can have a ``state'': cleared, pending, or uncleared.
|
||||||
The default is uncleared. To mark a transaction cleared, put a *
|
The default is uncleared. To mark a transaction cleared, put a *
|
||||||
|
|
@ -2700,6 +2715,7 @@ date.
|
||||||
|
|
||||||
@node Virtual postings, Expression amounts, Metadata, Transactions
|
@node Virtual postings, Expression amounts, Metadata, Transactions
|
||||||
@section Virtual postings
|
@section Virtual postings
|
||||||
|
@findex --real
|
||||||
|
|
||||||
Ordinarily, the amounts of all postings in a transaction must balance
|
Ordinarily, the amounts of all postings in a transaction must balance
|
||||||
to zero. This is non-negotiable. It's what double-entry accounting
|
to zero. This is non-negotiable. It's what double-entry accounting
|
||||||
|
|
@ -2955,6 +2971,7 @@ or @@@@ with parentheses:
|
||||||
|
|
||||||
@node Commodity prices, Prices vs. costs, Virtual posting costs, Transactions
|
@node Commodity prices, Prices vs. costs, Virtual posting costs, Transactions
|
||||||
@section Commodity prices
|
@section Commodity prices
|
||||||
|
@findex --lot-prices
|
||||||
|
|
||||||
When a transaction occurs that exchange one commodity for another,
|
When a transaction occurs that exchange one commodity for another,
|
||||||
Ledger records that commodity price not only within its internal price
|
Ledger records that commodity price not only within its internal price
|
||||||
|
|
@ -3136,6 +3153,7 @@ found in @ref{Prices vs. costs}.
|
||||||
|
|
||||||
@node Lot dates, Lot notes, Fixated prices, Transactions
|
@node Lot dates, Lot notes, Fixated prices, Transactions
|
||||||
@section Lot dates
|
@section Lot dates
|
||||||
|
@findex --lot-dates
|
||||||
|
|
||||||
In addition to lot prices, you can specify lot dates and reveal them
|
In addition to lot prices, you can specify lot dates and reveal them
|
||||||
with @code{--lot-dates}. Other than that, however, they have no
|
with @code{--lot-dates}. Other than that, however, they have no
|
||||||
|
|
@ -3152,6 +3170,8 @@ expressions):
|
||||||
|
|
||||||
@node Lot notes, Lot value expressions, Lot dates, Transactions
|
@node Lot notes, Lot value expressions, Lot dates, Transactions
|
||||||
@section Lot notes
|
@section Lot notes
|
||||||
|
@findex --lot-notes
|
||||||
|
@findex --lots
|
||||||
|
|
||||||
You can also associate arbitrary notes for your own record keeping in
|
You can also associate arbitrary notes for your own record keeping in
|
||||||
parentheses, and reveal them with @code{--lot-notes}. One caveat is
|
parentheses, and reveal them with @code{--lot-notes}. One caveat is
|
||||||
|
|
@ -3449,6 +3469,7 @@ posting.
|
||||||
@node Effective Dates, Periodic Transactions, State flags, Automated Transactions
|
@node Effective Dates, Periodic Transactions, State flags, Automated Transactions
|
||||||
@subsection Effective Dates
|
@subsection Effective Dates
|
||||||
@cindex effective dates
|
@cindex effective dates
|
||||||
|
@findex --effective
|
||||||
|
|
||||||
In the real world transactions do not take place instantaneously.
|
In the real world transactions do not take place instantaneously.
|
||||||
Purchases can take several days to post to a bank account. And you may
|
Purchases can take several days to post to a bank account. And you may
|
||||||
|
|
@ -3524,6 +3545,7 @@ really knows that it debited $225 this month.
|
||||||
|
|
||||||
@node Periodic Transactions, Concrete Example of Automated Transactions, Effective Dates, Automated Transactions
|
@node Periodic Transactions, Concrete Example of Automated Transactions, Effective Dates, Automated Transactions
|
||||||
@subsection Periodic Transactions
|
@subsection Periodic Transactions
|
||||||
|
@findex --budget
|
||||||
|
|
||||||
A periodic transaction starts with a ~ followed by a period
|
A periodic transaction starts with a ~ followed by a period
|
||||||
expression. Periodic transactions are used for budgeting and
|
expression. Periodic transactions are used for budgeting and
|
||||||
|
|
@ -3683,7 +3705,6 @@ $ ledger balance -f drewr3.dat Auto MasterCard
|
||||||
$ -20.00 Liabilities:MasterCard
|
$ -20.00 Liabilities:MasterCard
|
||||||
--------------------
|
--------------------
|
||||||
$ 5,480.00
|
$ 5,480.00
|
||||||
20:39:21 ~/ledger/test/input >
|
|
||||||
@end smallexample
|
@end smallexample
|
||||||
|
|
||||||
@noindent
|
@noindent
|
||||||
|
|
@ -3700,7 +3721,6 @@ $ ledger balance -f drewr3.dat Income
|
||||||
$ -30.00 Sales
|
$ -30.00 Sales
|
||||||
--------------------
|
--------------------
|
||||||
$ -2,030.00
|
$ -2,030.00
|
||||||
20:40:28 ~/ledger/test/input >
|
|
||||||
@end smallexample
|
@end smallexample
|
||||||
|
|
||||||
You can use general regular expressions in nearly anyplace Ledger
|
You can use general regular expressions in nearly anyplace Ledger
|
||||||
|
|
@ -3768,6 +3788,10 @@ total; and report the balance for all accounts that begin with
|
||||||
|
|
||||||
@node Reporting monthly expenses, , Typical queries, Typical queries
|
@node Reporting monthly expenses, , Typical queries, Typical queries
|
||||||
@subsection Reporting monthly expenses
|
@subsection Reporting monthly expenses
|
||||||
|
@findex --monthly
|
||||||
|
@findex -M
|
||||||
|
@findex --display
|
||||||
|
@findex --period-sort
|
||||||
|
|
||||||
The following query makes it easy to see monthly expenses, with each
|
The following query makes it easy to see monthly expenses, with each
|
||||||
month's expenses sorted by the amount:
|
month's expenses sorted by the amount:
|
||||||
|
|
@ -3938,6 +3962,8 @@ tell Ledger what to do for the last line, in this case, nothing.
|
||||||
@cindex Gnuplot script
|
@cindex Gnuplot script
|
||||||
@cindex plotting
|
@cindex plotting
|
||||||
@cindex Gnuplot
|
@cindex Gnuplot
|
||||||
|
@findex --amount-data
|
||||||
|
@findex --total-data
|
||||||
|
|
||||||
If you have @command{Gnuplot} installed, you can graph any of the
|
If you have @command{Gnuplot} installed, you can graph any of the
|
||||||
above register reports. The script to do this is included in the
|
above register reports. The script to do this is included in the
|
||||||
|
|
@ -4093,6 +4119,7 @@ limiting and searching functions.
|
||||||
@cindex reading csv
|
@cindex reading csv
|
||||||
@cindex comma separated variable file reading
|
@cindex comma separated variable file reading
|
||||||
@findex convert
|
@findex convert
|
||||||
|
@findex --input-date-format
|
||||||
|
|
||||||
The @code{convert} command parses a comma separated value (csv) file
|
The @code{convert} command parses a comma separated value (csv) file
|
||||||
and outputs Ledger transactions. Many banks offer csv file downloads.
|
and outputs Ledger transactions. Many banks offer csv file downloads.
|
||||||
|
|
@ -4124,9 +4151,9 @@ Transaction Number,Date,Description,Memo,Amount Debit,Amount Credit,Balance,Chec
|
||||||
Unfortunately, as it stands Ledger cannot read it, but you can. Ledger
|
Unfortunately, as it stands Ledger cannot read it, but you can. Ledger
|
||||||
expects the first line to contain a description of the fields on each
|
expects the first line to contain a description of the fields on each
|
||||||
line of the file. The fields ledger can recognize are called
|
line of the file. The fields ledger can recognize are called
|
||||||
``@code{date}'' ``@code{posted}'', ``@code{code}'', ``@code{payee} or
|
@option{date}, @option{posted}, @option{code}, @option{payee} or
|
||||||
@code{desc}'', ``@code{amount}'', ``@code{cost}'', ``@code{total}'', and
|
@option{desc}, @option{amount}, @option{cost}, @option{total}, and
|
||||||
``@code{note}''.
|
@option{note}.
|
||||||
|
|
||||||
Delete the account description lines at the top, and replace the first
|
Delete the account description lines at the top, and replace the first
|
||||||
line in the data above with:
|
line in the data above with:
|
||||||
|
|
@ -4161,6 +4188,10 @@ transid,date,payee,note,amount,,,code,
|
||||||
Ledger will include @code{; transid: 767718} in the first transaction
|
Ledger will include @code{; transid: 767718} in the first transaction
|
||||||
is from the file above.
|
is from the file above.
|
||||||
|
|
||||||
|
@findex --invert
|
||||||
|
@findex --account NAME
|
||||||
|
@findex --rich-data
|
||||||
|
|
||||||
The @code{convert} command accepts three options, the most important
|
The @code{convert} command accepts three options, the most important
|
||||||
ones are @code{--invert} which inverts the amount field, and
|
ones are @code{--invert} which inverts the amount field, and
|
||||||
@code{--account NAME} which you can use to specify the account to
|
@code{--account NAME} which you can use to specify the account to
|
||||||
|
|
@ -4721,6 +4752,7 @@ pricedb database files.
|
||||||
|
|
||||||
@node Reports about your Journals, , Reports in other Formats, Reporting Commands
|
@node Reports about your Journals, , Reports in other Formats, Reporting Commands
|
||||||
@section Reports about your Journals
|
@section Reports about your Journals
|
||||||
|
@findex --count
|
||||||
|
|
||||||
@menu
|
@menu
|
||||||
* accounts::
|
* accounts::
|
||||||
|
|
@ -4744,8 +4776,9 @@ account.
|
||||||
@subsection @code{payees}
|
@subsection @code{payees}
|
||||||
@findex payees
|
@findex payees
|
||||||
|
|
||||||
The @command{payees} reports all of the unique payees in the
|
The @command{payees} reports all of the unique payees in the journal.
|
||||||
journal. To filter the payees displayed you must use the prefix:
|
Using the @code{--count} option will tell you how many entries use
|
||||||
|
each payee. To filter the payees displayed you must use the prefix:
|
||||||
|
|
||||||
@smallexample
|
@smallexample
|
||||||
$ ledger payees @@Nic
|
$ ledger payees @@Nic
|
||||||
|
|
@ -4766,6 +4799,7 @@ tell you how many entries use each commodity.
|
||||||
@node tags, entry and xact, commodities, Reports about your Journals
|
@node tags, entry and xact, commodities, Reports about your Journals
|
||||||
@subsection @command{tags}
|
@subsection @command{tags}
|
||||||
@findex tags
|
@findex tags
|
||||||
|
@findex --values
|
||||||
|
|
||||||
The @command{tags} reports all of the tags in the journal. The output
|
The @command{tags} reports all of the tags in the journal. The output
|
||||||
is sorted by name. Using the @code{--count} option will tell you how
|
is sorted by name. Using the @code{--count} option will tell you how
|
||||||
|
|
@ -5179,7 +5213,7 @@ GUIs, which would make use of the different scopes by keeping an
|
||||||
instance of Ledger running in the background and running multiple
|
instance of Ledger running in the background and running multiple
|
||||||
sessions with multiple reports per session.
|
sessions with multiple reports per session.
|
||||||
|
|
||||||
@table @code
|
@ftable @code
|
||||||
@item --args-only
|
@item --args-only
|
||||||
Ignore all environment and init-file settings and
|
Ignore all environment and init-file settings and
|
||||||
use only command-line arguments to control Ledger. Useful for debugs
|
use only command-line arguments to control Ledger. Useful for debugs
|
||||||
|
|
@ -5234,7 +5268,7 @@ a function called @code{normalize_options}.
|
||||||
|
|
||||||
@item --script <PATH>
|
@item --script <PATH>
|
||||||
Execute a ledger script.
|
Execute a ledger script.
|
||||||
@end table
|
@end ftable
|
||||||
|
|
||||||
@node Session Options, Report Options, Global Options, Detailed Options Description
|
@node Session Options, Report Options, Global Options, Detailed Options Description
|
||||||
@subsection Session Options
|
@subsection Session Options
|
||||||
|
|
@ -5302,7 +5336,7 @@ $ ledger -f test/input/drewr3.dat bal --master-account HUMBUG
|
||||||
$ 200.00 Mortgage:Principal
|
$ 200.00 Mortgage:Principal
|
||||||
@end smallexample
|
@end smallexample
|
||||||
|
|
||||||
@item --price-db <PATH>
|
@item --price-db FILE
|
||||||
Specify the location of the price entry data file.
|
Specify the location of the price entry data file.
|
||||||
|
|
||||||
@item --price-exp INTEGER_MINUTES
|
@item --price-exp INTEGER_MINUTES
|
||||||
|
|
@ -6488,6 +6522,8 @@ commodity can mean different things to different people, depending on
|
||||||
the accounts involved, the commodities, the nature of the transactions,
|
the accounts involved, the commodities, the nature of the transactions,
|
||||||
etc.
|
etc.
|
||||||
|
|
||||||
|
@findex --now
|
||||||
|
|
||||||
When you specify @code{-V}, or @code{-X COMM}, you are requesting that
|
When you specify @code{-V}, or @code{-X COMM}, you are requesting that
|
||||||
some or all of the commodities be valuated as of today (or whatever
|
some or all of the commodities be valuated as of today (or whatever
|
||||||
@code{--now} is set to). But what does such a valuation mean? This
|
@code{--now} is set to). But what does such a valuation mean? This
|
||||||
|
|
@ -6578,6 +6614,7 @@ valuated in another currency. For example:
|
||||||
|
|
||||||
@cindex FIFO/LIFO
|
@cindex FIFO/LIFO
|
||||||
@cindex LIFO/FIFO
|
@cindex LIFO/FIFO
|
||||||
|
@findex --lots
|
||||||
Ledger presently has no way of handling such things as FIFO and LIFO.
|
Ledger presently has no way of handling such things as FIFO and LIFO.
|
||||||
|
|
||||||
If you specify an unadorned commodity name, like AAPL, it will balance
|
If you specify an unadorned commodity name, like AAPL, it will balance
|
||||||
|
|
@ -6585,6 +6622,7 @@ against itself. If @code{--lots} are not being displayed, then it will
|
||||||
appear to balance against any lot of AAPL.
|
appear to balance against any lot of AAPL.
|
||||||
|
|
||||||
@cindex adorned commodity
|
@cindex adorned commodity
|
||||||
|
@findex --lot-prices
|
||||||
If you specify an adorned commodity, like AAPL @{$10.00@}, it will
|
If you specify an adorned commodity, like AAPL @{$10.00@}, it will
|
||||||
also balance against itself, and against any AAPL if @code{--lots} is
|
also balance against itself, and against any AAPL if @code{--lots} is
|
||||||
not specified. But if you do specify @code{--lot-prices}, for
|
not specified. But if you do specify @code{--lot-prices}, for
|
||||||
|
|
@ -6724,6 +6762,9 @@ weekly last august
|
||||||
|
|
||||||
@node Budgeting, Forecasting, Budgeting and Forecasting, Budgeting and Forecasting
|
@node Budgeting, Forecasting, Budgeting and Forecasting, Budgeting and Forecasting
|
||||||
@section Budgeting
|
@section Budgeting
|
||||||
|
@findex --budget
|
||||||
|
@findex --add-budget
|
||||||
|
@findex --unbudgeted
|
||||||
|
|
||||||
Keeping a budget allows you to pay closer attention to your income and
|
Keeping a budget allows you to pay closer attention to your income and
|
||||||
expenses, by reporting how far your actual financial activity is from
|
expenses, by reporting how far your actual financial activity is from
|
||||||
|
|
@ -6789,6 +6830,7 @@ You can also use these flags with the @command{balance} command.
|
||||||
|
|
||||||
@node Forecasting, , Budgeting, Budgeting and Forecasting
|
@node Forecasting, , Budgeting, Budgeting and Forecasting
|
||||||
@section Forecasting
|
@section Forecasting
|
||||||
|
@findex --forecast
|
||||||
|
|
||||||
Sometimes it's useful to know what your finances will look like in the
|
Sometimes it's useful to know what your finances will look like in the
|
||||||
future, such as determining when an account will reach zero. Ledger
|
future, such as determining when an account will reach zero. Ledger
|
||||||
|
|
@ -7185,6 +7227,17 @@ Useful specifying a date in plain terms. For example, you could say
|
||||||
|
|
||||||
@node Basics, Format String Structure, Format Strings, Format Strings
|
@node Basics, Format String Structure, Format Strings, Format Strings
|
||||||
@section Format String Basics
|
@section Format String Basics
|
||||||
|
@findex --format
|
||||||
|
@findex -F
|
||||||
|
@findex --balance-report
|
||||||
|
@findex --cleared-report
|
||||||
|
@findex --register-report
|
||||||
|
@findex --csv-report
|
||||||
|
@findex --plot-amount-report
|
||||||
|
@findex --plot-total-report
|
||||||
|
@findex --pricedb-report
|
||||||
|
@findex --prices-report
|
||||||
|
@findex --wide-register-report
|
||||||
|
|
||||||
Format strings may be used to change the output format of reports.
|
Format strings may be used to change the output format of reports.
|
||||||
They are specified by passing a formatting string to the
|
They are specified by passing a formatting string to the
|
||||||
|
|
@ -7344,6 +7397,8 @@ same format string is used for all postings.
|
||||||
|
|
||||||
@node --balance-format, Formatting codes, Format Expressions, Format Strings
|
@node --balance-format, Formatting codes, Format Expressions, Format Strings
|
||||||
@section --balance-format
|
@section --balance-format
|
||||||
|
@findex --balance-format
|
||||||
|
@findex --format
|
||||||
|
|
||||||
As an example of how flexible the @code{--format} strings can be, the
|
As an example of how flexible the @code{--format} strings can be, the
|
||||||
default balance format looks like this (the various functions are
|
default balance format looks like this (the various functions are
|
||||||
|
|
@ -7427,6 +7482,7 @@ terminal character colors and font highlights in a normal TTY session.
|
||||||
|
|
||||||
@node Dates, Date and Time Format Codes, Quantities and Calculations, Formatting codes
|
@node Dates, Date and Time Format Codes, Quantities and Calculations, Formatting codes
|
||||||
@subsection Date Functions
|
@subsection Date Functions
|
||||||
|
@findex --now
|
||||||
|
|
||||||
The following functions allow you to manipulate and format dates.
|
The following functions allow you to manipulate and format dates.
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue