Hi Gail,

There's a base class method that you can use called DebugLog() that you can use to write out messages to a text file durring runtime of the DLL. However, I think your issue may be security related. Try putting the DBC on a local share (local to the components) and enable full access to everyone to see if that works. If it does, you can adjust the security settings as necessary.

Have fun,
-B

>Thanks. That's what I suspected.
>
>
>>You can't debug into COM components. You'll need to write the information out to a log.
>>
>>
>>>I have tried to set breakpoints, but either I'm missing the point of failure with my breakpoint, or else these .dlls can't be debugged that way. I'm not sure how else to check the path.
>>>
>>>
>>>>Try to check the path and file name at the time of the error.
>>>>
>>>>>Thanks. I checked that out and the path I have is correct.
>>>>>
>>>>>>See Re: Problems instantiating the Attorney sample object. Thread #670123 Message #671807.
>>>>>>
>>>>>>>I downloaded the latest version and am working with the sample app (attorney app). I began working with this using VFP7, but when I had trouble I also tried it using VFP6 and had the same result.
>>>>>>>
>>>>>>>In the part of the documentation where you test your Attorney app the first time by entering the following in the command window:
>>>>>>>oAttorney = createobject('AttResMgr.Attorney')
>>>>>>>rs = oAttorney.GetProxy()
>>>>>>>
>>>>>>>I get the following error:
>>>>>>>
>>>>>>>OLE IDispatch exception code 429 from Attorney: ~Error: 1429 Line: 18 AttorneyDataSource::Openconnectionobject() OLE IDispatch excetion code 0 from Microsoft OLE DB Provider for Visual Foxpro: Invalid path or file name...
>>>>>>>
>>>>>>>Can anyone help?