>>>I have a VFP6/SP3 form with an MSTreeView
>>>inside it which is populated by a
>>>(non-paramaterized) remote view of a VFP
>>>DBC table. The form works well in the
>>>development environment, but when I compiled
>>>it into an .app and ran it as an
>>>ActiveDocument inside IE4, the VFP
>>>ODBC driver spit back "access denied".
>>>
>>>I created the view programatically with the "shared" clause.
>>>
>>>Looking at the Data Environment properties
>>>on the form, I saw that the properties
>>>on the view were set Exclusive .t. -
>>>italicized so I could not change it.
>>>I think the exlcusive property is what's
>>>getting me into trouble, although I am not
>>>sure how or why.
>>>
>>
>>More than likely that the user executing the
>>ActiveDoc doesn't have access rights to
>>the directory (or individual file file
>>if an NTFS drive is being referenced)
>>and the operating system is denying
>>access to the the file. I'm assuming
>>that you're using some form of UNC
>>reference to specify the file, since
>>the context of execution for an ActiveDoc
>>is the client system rather than
>>the server that delivers the ActiveDoc.
>
>
>Thanks, but all of this is happening on
>my development system (WinNT) where I have full
>Administrator rights&perms. I am not even
>using UNC, I am just using standard Windows
>drive letter notation "e:\src\projects\weblibrary\data\weblib.dbc"
>

The only times I've seen this under NT are where the user didn't have adequate permissions (and you still may not be really aware of what permissions you have from within your browser, but that's a different issue. More importantly, once this goes up so that other machines will access the app, the path you're using won't be valid.) or where something other than the current VFP instance had the file open in a mode that denied access (IOW, if you wanted to get shared access and some other process, like another instance of VFP, had the file open exclusively, you'd get the "File access is denied" message.)

>
>Help more? :)