On 12 June 2009 at 08:41, [email protected] wrote:
| On Thu, Jun 11, 2009 at 08:41:13PM -0500, Dirk Eddelbuettel wrote:
| >
| > Henry,
| >
| >
| > On 11 June 2009 at 15:01, [email protected] wrote:
| > |
| > |
| > | On Thu, Jun 11, 2009 at 06:43:31AM -0500, Dirk Eddelbuettel wrote:
| <snip>
| > we may not have added information on its currency. On the other hand, if
you do
| >
| > beancounter addportfolio HEXA-B.ST:100:SEK:foo:bar:73.50:20090611
|
| Used this originally. If I check the table "Portfolio" then HEXA-B.ST shows
| as currency SEK.
| >
| <snip>
| >
| > Wrong -- you need
| >
| > beancounter --extrafx SEK update
| >
| Ran this and it worked.
|
| Many thanks
|
| Oddly enough I received the following error messages
|
| Use of uninitialized value $b[2] in join or string at
/usr/share/perl5/Finance/YahooQuote.pm line 88.
| Ignoring symbol ^XCV with unparseable date
| Ignoring symbol ^XEU with unparseable date
Yes, that is the 'Yahoo for daily data problem'. The code I have here has a
an alternative to Yahoo! for _historical_ data, which is different (as it
applies to 'fxbackpopulate' only.
We can the --ubcfx option which uses the service at the Univ of British
Columbia in Vancouver. So also try
beancounter --ubcfx --extrafx SEK update
| I will come back to you on this as I want to check my data first: it
| could be due to sloppy entering of data.
Ok. Yahoo! does create warnings. We may need to think about a new source for
FX.
| > |
| > | VERY little knowledge of PERL and SQL but willing to learn
| >
| > Good good good, you may well end up doing some really useful testing.
| >
| Willing and able. Let me come back to you later: I have copied the
| database (I am using sqlite3) and am going through cleaning out old
| records (eg shares sold are marked as "sold" and hence I can track bad
| decisions).
|
| PS I did buy a book on Perl as I wanted to understand the program as I
| find it incredibly useful. But got lost ...
:)
Dirk
--
Three out of two people have difficulties with fractions.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
