Roi;

OK - you've been a great help. You helped me get around the attribute problem before (I'm living with scanning ALL rather than limiting the scope as I hoped to do). This time, I suspect I'm gonna have to go and learn how to create VB6 generated ActiveX components (as was suggested by Michael Mead in this thread) if I wanna take this further in VFP.

It's just gonna complicate application distribution a little...

Michael

>Hi Michael,
>
>I think the problem is in the array. I played around with it a little and always get the same error. I tried using ComArray() to try and pass it as a 0-based array (which is what I think ACAD wants) but to no joy.
>
>I think this was the same problem you were having with the filter and searching for blocks with attributes before.
>
>Sorry I can't be of more help.
>
>>Hey, Roi;
>>
>>I've been doing some experimenting with this stuff, too. I have been able to assign an ACAD point to an array (returns as Numeric) using:
>>
>>ACAD = GetObject(,"AutoCAD.Application")
>>DOC = ACAD.ActiveDocument
>>inspoint=DOC.Utility.Getpoint(, "Select Point: ")
>>
>>But, when I try to proceed and insert a block (a file, actually) at that point with:
>>
>>DOC.ModelSpace.InsertBlock(InsPoint, "G:\CADD\DETAILS\PresFurn.DWG",1,1,0)
>>
>>I get back the error:
>>OLE IDispatch exception code 0 from AutoCAD Application:
>>Invalid argument insPoint in InsertionPoint property
>>
>>I was assuming it's whining because of the TYPE - because I swear I'm using the exact same variable I got from ACAD in the lines above! Gee - you'd think ACAD would take it back in the same format it gives it out!?!?!?
>>
>>Can you help me understand this behaviour?
>>