You're developing on your desktop, right? Do not remove. It should be registered there.
Cetin

>Well, I removed it from my desktop where I am developing VS.net and now I get the error "The VFPOLEDB.1 provider is not registered on the local machine". OOps!
>
>>No not the users, server must have it. User might be accessing from say a PlayStationPortable (inspired from my son:) which has no db driver on it.
>>Cetin
>>
>>>I've got that VFPOLEDB on my system but when my asp server goes production, will it need to be on that or does every user on the internet who accesses the web site have to have it on their desktops?
>>>
>>>>No Tim,
>>>>It's OLEDB driver (VFPOLEDB must exist).
>>>>Cetin
>>>>
>>>>>Cetin, I too am trying to setup a conection to my vfp tables from VS net but wonder if the odbc driver has to be on the server?
>>>>>
>>>>>
>>>>>
>>>>>>>Hi All,
>>>>>>>I am trying to connect to my VFP data using OLEDB in ASP.NET
>>>>>>>
>>>>>>>

>>>>>>>Conn = New System.Data.OleDb.OleDbConnection(
>>>>"provider=VFPOLEDB.1; data source='" & MyDataSource & "'")
>>>>>>>Conn.Open()
>>>>>>>

>>>>>>>
>>>>>>>Then here's what I get:
>>>>>>>
>>>>>>>

"Non-NULL controlling IUnknown was specified,
>>>>and either the requested interface was not IUnknown,
>>>>or the provider does not support COM aggregation."
>>>>>>>

>>>>>>>I tried in the other server with exactly the same settings/configurations and it is ok.
>>>>>>>Any Idea?
>>>>>>>
>>>>>>>Thanks
>>>>>>>
>>>>>>>Jay
>>>>>>
>>>>>>From an ASP this works for me just right:
>>>>>>

>>>>>>    dbpath = Server.MapPath("data")
>>>>>>' ADO connection ...
>>>>>>  .ConnectionString = "Provider=VFPOLEDB;data source=" & dbpath & "\myDatabase.dbc"
>>>>>>

Cetin