Hi Kyrene!<br>
<br>
OK, I misunderstood the question -- that 'dot' in '.com' threw me off! Too many things, not enough names for them all.<br>
<br>
Simply put, VB has had the ability to create COM objects since version 4. What you do is create a Active-X DLL project, add a class module, and then set the instancing properties for the class as a whole to "5 - Multiuse". Any methods (properties, functions, subroutines) and variables that you declare as "public" in this class become visible to other programs, and available for their use.<br>
<br>
So, if CF has the ability to call COM and DCOM objects, then there shouldn't be any problems calling a COM object written in VB. One catch, is if you distribute your VB COM object, you also have to distribute the VB runtime.<br>
<br>
Chip H.<br>