>Thomas,
>
>I was hoping someone was going to suggest an activeX.
>
>Thanks for the Visio idea - have you done this?
>How easy was it to do?

I have not used Visio in a COM object, but I would not expect to be very different from any other COM object using the Microsoft Object Model(Excel, Word and the rest of the Office suite).

Do some stuff in visio with the record macro turned on and stop recording when you have seen enough. Open the VBA editor and view the macro that Visio wrote.
This macro is what you use to build your foxpro routine. The code is very similar to Fox, so you can get a sense of what Visio is doing.

Sending your Fox routines to Visio will not be a problem. Sending your edits in Visio back to Fox, will have the same degree of difficulty as sending update's from word, access, excel etc.

You will need a header file for Visio's type definitions. The editor in VBA will let you view the visio.ol* file. Grab a copy of this file and paste it in a new text file. In UT's file section there is a utility to parse this text to create the header.

All this sounds worse than it really is. Once you remember to put a period in front of the VBA commands and change the VBA format of using named parameters, it is almost like writing Fox code.