Thanks Ed, I think it may have the foxuser file in my case. I was trying to run it against different projects as a test (since it bombed out on the one I needed to run it against) and it bombed everytime. When I finally got it working, I had deleted my foxuser file in between there somewhere also. I also switched from spaces to tabs for indentation and told it not to change the capitalization and it worked for some reason. Frustrating! My intention in running it was to get the variables used in the project as well as the 'used by' headings. It doesn't provide a 'used by' heading anylonger (wonder why not?)

By the way, any idea how to list all of the arrays used in a project? I finally got the documentation wizard to work on my project and even with a 9.4mb xref.lst file it still doesn't show the arrays. Almost all of our critical information is stored in arrays in the project. This is what happens when you pick up an app that was written 10 years ago to convert it to VFP7 and there is little if any documentation!

TIA,

Tracy

>>VFP7 SP1. Any idea why I would get an Error #2028: API Call Caused an exception when running the documentation wizard on my project? In the program it is currently processing: main.prg, the next line of code is:
>>
>
>Tracy, I think the API call is actually in the documentation wizard itself, not in your code; I remember seeing this problem with VFP6 as well at one point. SWAG, but based on cryptic notes to myself, try cleaning out your FOXUSER file immediately before running the documentation wizard, as well as the registry key HKCU\Software\Microsoft\VisualFoxpro\7.0\Options\IDE (you might want to save this hive somewhere, since a number of the VFP IDE Options are stored there for the current user, and I don't know which if any of them was offensive...)
>
>>CRNT_BLD = ""
>>
>>hardly offensive.
>>
>>The time before that it stopped at:
>>
>>m.ag_cltype = 1 && 1 = Prime Rate, 2 = RPM
>>
>>I did have an api call in the main.prg, but when I got this error message the first time, I remarked it out, and then I cut it out completely so I could run the documentation wizard.
>>
>>Any ideas?
>>
>>TIA,
>>TRACY