> The questions I have are what API are available, what specific functions do > they perform, how are they called, what parameters are passed/results > returned, etc.? I know there are more API around than can be covered here. > But I think with all the knowledge floating around the UT, a really good > "VFP API Knowledge Base" could be developed. I don't know about the > legalities of it, but maybe this particular base (if extensive enough) > could be compiled into a single resource guide, and sold through the > UT/VFUG at a nominal cost to help defray costs of the FREE VFUG and the > FREE part of the UT. Those posting would be asked to "donate there > knowledge." I am just thinking out loud here, but I hate to see VFUG > officers shelling out $$$ for a service that is so valuable to all of us. Mark, VFUG is no longer related in any way to the UT , it is indendependent and has its own site and domain (www.vfug.org btw (s)) all VFUG services are free and we really hope we do what ever we can so that it would stay that way at now to the point we (Tom, Scot and myself) are building our site and the tips and FAQ sections are now under major reconstruction to make them much more usable any (working) addition to this that would be submitted would be put on-line btw i published 2 articles on using the API with VFP in the VFUG newsletter , and considering the feedback I've got I guess they are ok (s) Arnon