FoxPro connect problems REGDB_E_CLASSNOTREG

[Paul]

I'm using vs.net, clr 1.1, c# web application. I get the following error
connecting to foxpro using its oledb driver. I've tried several ways to
connect.

No error information available: REGDB_E_CLASSNOTREG(0x80040154).
[OleDbException (0x80040154): No error information available:
REGDB_E_CLASSNOTREG(0x80040154).]

[InvalidOperationException: The 'vfpoledb.1' provider is not registered
on the local machine.]
System.Data.OleDb.OleDbConnection.CreateProviderError(Int32 hr)

System.Data.OleDb.OleDbConnection.CreateProvider(OleDbConnectionString
constr)
System.Data.OleDb.OleDbConnection.Open()
Elkhorn.eCatData.Page_Load(Object sender, EventArgs e) in
j:\projects\aproject\aproject\webui\data.aspx.cs:45
System.Web.UI.Control.OnLoad(EventArgs e)
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Page.ProcessRequestMain()

I downloaded and installed the driver foxpro8 driver from:
http://www.microsoft.com/downloads/...58-7a94-4ae1-a59e-965869cb3bc9&displaylang=en

I don't have any verison of foxprox on the machine. I registered
vfpoledb.dll myself from the command line just to make sure.
The connection tested ok with the "Test Connection" button when I used
the designer.
I think the connection string is fine, is as on connectionstrings.com.
@"Provider=vfpoledb.1;Data
Source=C:\progra~1\aproject\data\data1.dbc;Password=;Collating
Sequence=machine";


Any ideas?

???

 

[Guest]

I originally posted this in the data.oledb newsgroup but there doesn't seem to be much activity there

I got it to work by modifying the machine.config file. I changed the UserName value in the processmodel section to SYSTEM instead of MACHINE.

I don't like this solution because it grants the ASP.NET worker process too much power. I tried using a normal user account in the machine.config setting but it didn't help even when I set the user to be in the local administrators group. Only the SYSTEM account worked.

There has to be a better solution to this.

Well I thought I got it to work. It seems changing the processmodel username to SYSTEM only works if you are running Win XP. On Win2000 machines it doesn't make a difference.

 

[Guest]

The solution to this problem is to use the OLEDB driver that came with VFP 7. When using this version you do not have to make any changes to the machine.config file. I was able to access a VFP database from both an XP machine and a Win 2000 machine with no problem

It was hard to find the version 7 driver, I couldn't find it on the MSDN site. I had to create a setup file using the VFP OLEDB merge module that came with VFP 7

Gar

 

[bulls]

Garywrote:
I originally posted this in the data.oledb newsgroup but there
doesn't seem to be much activity there.

I got it to work by modifying the machine.config file. I changed the

UserName value in the processmodel section to SYSTEM instead of
MACHINE.

I don't like this solution because it grants the ASP.NET worker

process too much power. I tried using a normal user account in the
machine.config setting but it didn't help even when I set the user to
be in the local administrators group. Only the SYSTEM account worked.

There has to be a better solution to this.

Well I thought I got it to work. It seems changing the processmodel

username to SYSTEM only works if you are running Win XP. On Win2000
machines it doesn't make a difference.

Hi Gary,

I tried changing the machine.config setting according to your
instructions but to no avail. It still didnt work. Have the same
problem as paul... is there still anything we could do about it?

Do you know where i could get a copy of VFP provider ver 7.0?

I also tried using the server explorer, creating connections and data
sets but whenever i'll build it, i would go back to the same 'not
registered to the local machine.'

Please help! You may email me directly at (e-mail address removed).

Thanks a lot!
Bulls

*-----------------------*
Posted at:
www.GroupSrv.com
*-----------------------*

 

[bulls]

Garywrote:
I originally posted this in the data.oledb newsgroup but there
doesn't seem to be much activity there.

I got it to work by modifying the machine.config file. I changed the

UserName value in the processmodel section to SYSTEM instead of
MACHINE.

I don't like this solution because it grants the ASP.NET worker

process too much power. I tried using a normal user account in the
machine.config setting but it didn't help even when I set the user to
be in the local administrators group. Only the SYSTEM account worked.

There has to be a better solution to this.

Well I thought I got it to work. It seems changing the processmodel

username to SYSTEM only works if you are running Win XP. On Win2000
machines it doesn't make a difference.

Hi Gary,

I tried changing the machine.config setting according to your
instructions but to no avail. It still didnt work. Have the same
problem as paul... is there still anything we could do about it?

Do you know where i could get a copy of VFP provider ver 7.0?

I also tried using the server explorer, creating connections and data
sets but whenever i'll build it, i would go back to the same 'not
registered to the local machine.'

Please help! You may email me directly at (e-mail address removed).

Thanks a lot!
Bulls

*-----------------------*
Posted at:
www.GroupSrv.com
*-----------------------*

 

[bulls]

Garywrote:
I originally posted this in the data.oledb newsgroup but there
doesn't seem to be much activity there.

I got it to work by modifying the machine.config file. I changed the

UserName value in the processmodel section to SYSTEM instead of
MACHINE.

I don't like this solution because it grants the ASP.NET worker

process too much power. I tried using a normal user account in the
machine.config setting but it didn't help even when I set the user to
be in the local administrators group. Only the SYSTEM account worked.

There has to be a better solution to this.

Well I thought I got it to work. It seems changing the processmodel

username to SYSTEM only works if you are running Win XP. On Win2000
machines it doesn't make a difference.

Hi Gary,

I tried changing the machine.config setting according to your
instructions but to no avail. It still didnt work. Have the same
problem as paul... is there still anything we could do about it?

Do you know where i could get a copy of VFP provider ver 7.0?

I also tried using the server explorer, creating connections and data
sets but whenever i'll build it, i would go back to the same 'not
registered to the local machine.'

Please help! You may email me directly at (e-mail address removed).

Thanks a lot!
Bulls

*-----------------------*
Posted at:
www.GroupSrv.com
*-----------------------*