Mailing lists / fpc-pascal / 2009-04
5 messages · 3 people · –
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
I'm trying to compile a small executable in Win64 that makes use of the IFilter interface.
Registry read accesses are okay, the CoCreateInstance on IFilter and QueryInterface for an IPersistFile on the IFilter instance pass with ok results, but the first use of the interface (an IPersistFile.Load) dies with a RunError(1).
This is using the fpc 2.2.2 & ActiveX that comes with Lazarus (where IPersistFile is defined).
Is COM support functional in 2.2.2 Win64? Are there known issues?
Eric
Not sure if this is related, but 2.2.2 has a bug in setting properties via COM.
It should be resolved in 2.2.4
Bart
In our previous episode, Bart said:
Not sure if this is related, but 2.2.2 has a bug in setting properties via COM. It should be resolved in 2.2.4
As far as I know the winunits-base package had more than an handful other fixes also.
I've tried with FPC 2.2.5 (taken from the Lazarus daily snapshots page), and the same RunError(1) is still happening in the same place...
I can wrap up a test case as one lpr + one header unit, though to test it, one requires a Win64 machine with the Office 2007 64bit IFilters pack installed on it.
Eric
In our previous episode, Bart said: As far as I know the winunits-base package had more…
I've tried with FPC 2.2.5 (taken from the Lazarus daily snapshots page), and the same RunError(1) is still happening in the same place...
I can wrap up a test case as one lpr + one header unit, though to test it, one requires a Win64 machine with the Office 2007 64bit IFilters pack installed on it.
Eric