True, I will end up doing it from scratch. The user interface is probably
what I'd do anyway, so I could just copy some of the algorithms and save
some time.

There are a few questions, like the data storage format (I think he just
saved a dataset to disk, from what I can tell).

The really big question is what he used to export the data in .DOC format.
That would save me some time - or make it possible to show the folks who
paid him that there are copyright problems. What I mean by that: I suspect
he just wrapped up Microsoft's code (COM Callable Wrapper style) , and that
is a no-no, very serious one. If true, then they are so much better off not
shipping it per what the Ukrainian did.

I've posted another question about components that can preview data and
export to a .doc format. HTML and RTF are well supported, but DOC is not,
from what I've been able to determine by a 3 hour effort on line looking at
print/preview/report components.

Wes Davis

drv:
Thanks. I'd heard of it, but didn't have a bookmark - and remembering the
name from so many months ago was beyond me.

It does enough to save me some time, judging from a quick browse of some
core print preview stuff. It also appears the other developer (from the
Ukraine, for what that's worth), did wrap up Microsoft's stuff (Word,
Office) to do the .DOC file export. That is definitely a no-go. I'm glad I
know that, as whatever else happens, it will be without violating
copyrights. If nothing else, I needed this tool to make that determination.

Other routines, such as building HTML to export that way, I can largely copy
& paste. Again, a huge time saver. The user interface is the part I will do
from scratch, but the look is decent, so I can re-use that (visual design)
as-is and just create the code. Copying a layout is quick. The user
interface was not exotic - in fact it was too cheap in the code, as edits
did not even trigger a Dirty flag to ask to save changes.

Best Regards,

Wesley Davis