> The Dll is written in Delphi.
> I wasn't aware that looping in VFP code was so slow :-)

> Pete

Pete,

The VFP part of writing an engine is slow because it is interpreted from P-Code at runtime. If you want fast loops, it's best to write an FLL. I have considered writing part of the engine in C as an FLL for more speed. But it was easier to place the code into the Delphi Engine because I can then use it for making the ActiveX component more flexible in the future and possibly support OLEDB/ODBC built right into the ActiveX control without the need for being hosted in VFP to get to the data. It would still work in VB, Delphi and C++ as well. My main goal was to get a better Report Preview and have more flexible printing output as well. I'm not married to VFP FRX Reporting. I'm just supporting it so those in the VFP Community can have something a little more powerful.

Also, I find it amusing how much stuff is written in Delphi like this. Mine is written in Delphi too as well as the Ideal Software Virtual Print Engine mentioned in this thread. I think it's just a much more readable syntax than C/C++ and it's also got a great compiler with full source code to all of the libraries. Having the source helps a lot since you can make fixes or learn how some things are done and then improve upon them. However, there are a lot of VFP functions that you really miss. Just like those that Kamal rewrote into the VFP .NET Toolkit. So, if you want them you have to write them yourself. However, there is also that portability to Linux using Kylix. However, it's important to code it properly to be fully portable to Linux.