>x-cuse me for jumping in John. But can I ask why you are going from vb to vfp? I heard that MS has made it the "mandate" to do just the opposite. That's what's got everyone "frightened" about jumping to VB. No matter how much it doesn't match up to Vfp.

We need to implement an rpc call via a dll to a remote server which returns the string I send to it full of values for inventory, quantity, etc.

The documentation sample is vbcode. I need to make it work in VFP, our platform of choice. I connect to their server, but was getting an error code returned which said that the string was not null terminated. Hopefully CHR(0) will work.

Change topic....I'm waiting for the .net version of VB to start learning it. I figured since I've been using VFP since it came out, the learning curve will be easier if I wait for the totally OO version of VB.