>Actually, this ones a little trickier. AFIELDS, like a few other VFP data functions (to my infinite frustration) doesn't throw an error when there is no table open in the current area, it displays an Open dialog. Only after cancelling put of the dialog does the error get thrown.
>
>Paul, to solve your problem, just fix your code and make sure that there is a table open in the current work area. To try to avoid future issues like this, you can see if SYS(2335) will disable this dialog in your dll server (it is really meant for exe servers, but it might do the trick).

Thanks for your help everyone. It was an "error". This is turning into a big learning experience.

Am I correct in assuming that even though I do an create("myapp.myclass") on my dll and it's running in-process, that any tables that are open in VFP are not available to the process? For example, I have a table REPORT open and I want the dll to run some functions on it. If I just pass it the alias it won't be able to find it but if I pass it the filename it can open and process it. Correct?

paul