>In the same time, the problem is "cute" and sometimes it's just easier to use a VFP solution than to write a dll. The client may also require that all the code must be VFP (because the programmers that will maintain the code don't know C/C++). Another reason: not all VFP programmers can write a C/C++ dll and a solution like Cristof's class or my Pointers may help them cope without C/C++.

Here I disagree. If people don't understand C or the like it's unlikely
the concept of pointers or structures (maybe - after all VB supports
UDTs) is much of a help. You have to have much more knowledge about
Windows and how the Intel Architecture works by using these tools
than it is to write 3 lines of C code I think...

Whatever works I suppose. I prefer to use DLL code whenever I need to just
to keep the clutter and kludges out of the way. ActiveX controls are overkill
for many of these things and require registration and all sorts of other
system crap (the right MFC runtimes unless you're using ATL) that I stay
away from them unless there's enough functinoality and reuse to make it
worthwhile. Usign a DLL with a Class wrapper usually accomplishes the
same thing.

+++ Rick ---