When I export my scheduled transaction from Kmymoney to an icalendar file and then import them to Outlook (2007) it creates the calendar but says no application data is available and the calendar comes up with no transactions. I do have scheduled transactions in Kmymoney. Can anyone shed some light as to what I am doing wrong? (I have the plugin enabled)
Thanks,

Can you try viewing the iCalendar file in a text editor, to verify it has been successfully generated and contains valid content?

Yes, when opening in a text editor I do see my scheduled transactions. The actual message when importing to Outlook is "...file does not contain any appointments". I incorrectly said "applications" in my original post.
Thanks

Is the iCalendar file treated correctly by other applications which can handle iCalendar data?
This could be an Outlook specific bug, or it could be a bug in the generation process.

Outlook is supposed to handle icalendar. It imports the calendar, but for some reason no data. Oh well...thanks!

Sorry to rise this old post again but I have the same problem when importing to Google Agenda. The file contains all my appointments but after importing to google it says "Processed zero events". Have you get solve this problem?

Edit:
Checking for validity of the ical file generated by the plugin and got this:

Problem! Found 1 warning
Warnings
Expecting UTF-8 character set (detected UTF-8 encoding) near line # 1
Reference: RFC 5545 3.1.4. Character Set

Problem! Found 22 errors
Errors
Missing DTSTAMP property near line # 4
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 23
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 42
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 61
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 80
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 99
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 118
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 137
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 156
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 175
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 194
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 213
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 232
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 251
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 270
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 289
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 308
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 327
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 346
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 365
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 384
Reference: RFC 5545 3.6.2. To-Do Component
Missing DTSTAMP property near line # 403
Reference: RFC 5545 3.6.2. To-Do Component