willemstein
New Member
Hi
Started a week ago, and it's still a struggle.
First, importing. This is no trivial excercise, partly because I find the documentation lacking, and partly because the dutch translation is not brilliant. Was this done by a native speaker? If so, he/she was likely not a dutch national - it simply does not feel like dutch, in places. The dutch Localizable.strings file has a lot of errors.
An actual problem:
After I had figured out, with much trial & error (docs!!), how a transactions file should look I started Applescripting the conversion from my bank's data to some that iCash would understand (lots of dumb work, eh?).
The results seemed erratic. At some point I thought this had something to do with mixed text encoding in the script's output, but I'm not sure about that.
One thing I *did* find is that data are not imported when the file contains some transactions with an empty "payee" field: the documentation claims this field is optional. But what does "optional" mean? Is it "this field can be absent in the datafile" or "this field can be empty in one or more transactions"?
And:
~/Documents/Maxprog/ contains only data generated by the app, so it does not belong in the user's documents folder. It should be in ~/Library/Application Support/.
But then, OfficeMac shows the same nonstandard behaviour...
And:
The autobackup feature is another problematic area. I'll report about that in another post.
And:
The documentation seems to be for v. 4, but quite a few things look different in v. 5.
But, finally:
I discovered several errors in my existing system (in Excel). So, iCash's 'core functionality' is fine. It's just that some of the rough edges are *very* rough, in my early experience.
And everything here is just my opinion.
Started a week ago, and it's still a struggle.
First, importing. This is no trivial excercise, partly because I find the documentation lacking, and partly because the dutch translation is not brilliant. Was this done by a native speaker? If so, he/she was likely not a dutch national - it simply does not feel like dutch, in places. The dutch Localizable.strings file has a lot of errors.
An actual problem:
After I had figured out, with much trial & error (docs!!), how a transactions file should look I started Applescripting the conversion from my bank's data to some that iCash would understand (lots of dumb work, eh?).
The results seemed erratic. At some point I thought this had something to do with mixed text encoding in the script's output, but I'm not sure about that.
One thing I *did* find is that data are not imported when the file contains some transactions with an empty "payee" field: the documentation claims this field is optional. But what does "optional" mean? Is it "this field can be absent in the datafile" or "this field can be empty in one or more transactions"?
And:
~/Documents/Maxprog/ contains only data generated by the app, so it does not belong in the user's documents folder. It should be in ~/Library/Application Support/.
But then, OfficeMac shows the same nonstandard behaviour...
And:
The autobackup feature is another problematic area. I'll report about that in another post.
And:
The documentation seems to be for v. 4, but quite a few things look different in v. 5.
But, finally:
I discovered several errors in my existing system (in Excel). So, iCash's 'core functionality' is fine. It's just that some of the rough edges are *very* rough, in my early experience.
And everything here is just my opinion.
