pilot-read-expenses - Man Page

Export Palm Expense application data in a text format.

Section

pilot-link: Userland conduits

Synopsis

pilot-read-expenses [-p|--port <port>] [-q|--quiet] [--version] [-?|--help] [--usage] [-w|--write]

Description

pilot-read-expenses is used to output the Expense data in a simple text format, which can be used to import into any other application you wish, such as Excel or other application.

If you have expense entries saved on your Palm in the ExpenseDB.pdb file, you can export them to a simple text format, and redirect that to a file/pipe, or STDOUT (the default) using pilot-read-expenses.

The output data will resemble something like the following:

            Category: Unfiled Type:   5 Payment:   7 Currency:  23 Amount: 400.00 Vendor: Super Salads City: Westerly
            Attendees: Joe, Mary, Bob Note: Some simple note text Date: Fri May 9 00:00:00 2004

Options

pilot-read-expenses option

                       -w, --write
                   

Write out the expense data

Conduit Options

                       -p, --port port
                   

Use device file <port> to communicate with the Palm handheld. If this is not specified, pilot-read-expenses will look for the $PILOTPORT environment variable. If neither are found or supplied, pilot-read-expenses will print the usage information.

                       -q,
                       --quiet
                   

Suppress 'Hit HotSync button' message

                       -v, --version
                   

Display version of pilot-read-expenses and exit without connecting.

Help Options

                       -h, --help
                   

Display the help synopsis for pilot-read-expenses and exit without connecting.

                       --usage
                   

Display a brief usage message and exit without connecting.

Author

pilot-read-expenses was originally written by Kenneth Albanowski.

This manual page was converted to XML by Neil Williams <linux@codehelp.co.uk>

Reporting Bugs

We have an online bug tracker. Using this is the only way to ensure that your bugs are recorded and that we can track them until they are resolved or closed. Reporting bugs via email, while easy, is not very useful in terms of accountability. Please point your browser to http://bugs.pilot-link.org: http://bugs.pilot-link.org and report your bugs and issues there.

See Also

pilot-link(7)

See Also

install-expenses (1), pilot-link(7).

Info

Copyright 1996-2007 FSF 0.12.5 PILOT-LINK