Hi Sergey,
I thought we (the customer network admin and I) made sure that the account does have the access rights. But as I was reading today about the ASP.NET security and relations between local account and domain accounts and active directories, I am sure we missed something. I understand much more about these things now than I did on Friday when I was really kind of doing trial and error approach. I will talk to the admin next week (I wish I could go there again, but they are out of town - in CT) and hopefully we will get it working with over-the-phone instructions.
Thank you for your help.
P.S. The downside of learning this ASP.NET security is that I burned myself at the beach while reading this stuff (I didn't pay attention to the time) <g>.
>Hi Dmitry,
>
>Did you check if account that ASP.NET runs under has access rights to the VFP data on the other server?
>
>>The title of the message is not complete because of the limit of space.
>>
>>I have been having the following problem. A simple ASP.NET application needs to access VFP database via Ole Db. The data access is for read only.
>>All works well when the VFP data is on the save box (PC) as the web server. But when the data is on a difference server I get error message that Password and User name are required or not valid (something like that). The error message happens to be right on the Ole Db call so I figured that there is something to do with user rights.
>>
>>What should be the setting in the web.config to allow ASP.NET open table on another server. Again, this is for read only so security is not my concern.
>>I just want it to work <g>.
>>
>>Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham