>>>>grasping here, but why don't you try returning a value from the method you call in your server, and see if it makes a difference. Also, try putting a copy of your data in a virtual folder, use that data and see if makes a difference. We can then know for sure whether it is indeed a rights issue.
>>>
>>>I tried returning a value from the Method with no difference. I then copied the data file from the subfolder into the parent folder where the dll is running and changed the USE statement to reflect that. Still no difference. Hmmm....
>>
>>Parent? Try them in a subfolder of the webroot.
>
>No difference. It's kind of comical at this point, glad I'm not the type to fly off the handle!
>
>As a thought, I remember using a "patched" version of RegSvr32 once to register a VFP component. I never asked why, just did what I was told to do. Is there some reason for using a patched version of RegSvr32, and is it required for VFP components?

Does your component have something in the error method that would cause it to not throw errors? You need to simplify this a bit. How about putting code in your server to tell you whether a USE was successful or not? I still don't see why you're not getting errors.

If you have VFP on the web server machine, you can make sure the component is registered by instanciating it there. If not, you can do the same thing from a vbs file with the WSH. I have never heard of a 'patched' version of RegSvr32, but I doubt that has anything to do with it. If your component was not registered, you should be getting an error from ASP.