>
>
>You can!!!!! That's what ActiveX automation is all about. Create an automation server in VFP
>and then call it from VC++, VB, etc.

This is not feasible. The only way to send table/cursor data through ole automation to VB/VC++ is with a string. In VFP you would have to create something like a for...endfor loop that would sit there and concatenate each record so that it could be sent to VB. Have you ever timed FoxPro string routines???? They are performance dogs! I once had to lock a number of records at one time and I saw that the lock routine could accept either a recno or a series of recnos separated by commas in a string. As it turned out, creating the string became prohibitive. It was several hundred percent faster to create an array of all the recnos that I needed to lock and then with a for...endfor loop lock each record.

I have nothing against the FoxPro string handling system. It is optimized for ease of use and for short string handling operations. At the Fox devcon one of the sessions stated suggested to use the FOpen/FWrite file handling operations to write out the information you needed to disk and then to read the temporary file into a string from disk. Amazingly enough this operation was much faster than string concatenation! So until FoxPro creates a mechanism to send large amounts of table information via an ole, using Fox as an ole backend is out of the question.

Peter