From: david@NOSPAMdbarber.com   
      
   Why not just compile the code they have sent you, and use that for your   
   control?   
      
       *David*   
      
   "Phil Freed"  wrote in message   
   news:kcp6p0tbpih8hpn1b9n7q4q3ribq9fiqdm@4ax.com...   
   > We have a (commercial) program that comes with Visual Basic source   
   > code.  Unfortunately, the source code doesn't quite match the   
   > executable, which I determined by analyzing the memory returned by   
   > calls to the DLL.   
   >   
   > We're just off by byte here and there -- but the .DLL is kinda picky   
   > about those things.     
   >   
   > The company in question has sent us several revisions to the source,   
   > and we're getting closer.  In the meantime, I'm wondering if there's   
   > something I can do to in order to either (1) extract data structures   
   > from the DLL, or (2) do a "snoop" of the conversation between the DLL   
   > and the program.   
   >   
   > I should point out that Microsoft  VB is not my native tongue -- I'm   
   > more of a Perl/C/Unix kinda guy.   
   >   
   > Thanks in advance.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)