Configuration Error

[dday9]

I'm getting this error message:

Configuration system failed to initialize

When I try to debug. All I've done is:

1. Start a new windows form application
2. Add a new datasource
3. Drag the dgv from my datasource window to the form

I'm using MS Access 2003 and Vb Exp 2010. If I try to fill a datagridview manually, it works. Any reason why all of a sudden it does this?

[dday9]

It's been 2 days, so even though I hate when other people do it, Imma do it...
<short message>

[techgnome]

It sounds like it's trying to read something from the config file (like the connection string) and it can't... either because the config file is screwed up somehow, or the connectionstirng isn't in there.

-tg

[dday9]

That's what I don't get. I haven't altered my config file at all. And when I set up the datasource I verified the connectionstring as well as tested the connection.

[techgnome]

That doesn't mean something else didn't alter it...

Have you looked in the app.config file and verified that the connection string is there and that it is correct?

-tg

[dday9]

This is what's in my app.config file

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
</configSections>
<connectionStrings>
<add name="WindowsApplication1.My.MySettings.datesConnectionString"
connectionString="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=|DataDirectory|\dates.mdb"
providerName="System.Data.OleDb" />
</connectionStrings>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0,Profile=Client" />
</startup>
</configuration>

And also in my error list I have 3 errors:

Message	1	Could not find schema information for the element 'supportedRuntime'.	C:\Documents and Settings\PC 	11	10	

Message	2	Could not find schema information for the attribute 'version'.	C:\Documents and Settings\PC 	11	27	

Message	3	Could not find schema information for the attribute 'sku'.	C:\Documents and Settings\PC 	11	42

Edit - My target framework is .net framework 4.0 client profile

[.paul.]

did you try setting your target cpu to x86?
i don't think there's a 64 bit driver for Jet.OLEDB.4.0

[dday9]

I think by default it's set at x86. I would have to check the other computer when I get back to work. The thing is, it worked everytime without a hitch until I had low disk space. Now, even though I cleared my disk space up, I still get that error.