multiple-step ole db operation error opening ADO connection.

I am trying to Open an OLE DB connection to my Visual FoxPro connection.  On the open statement, I am getting an error saying "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done".  This exact same connection opens fine on a different PC but only on my new PC does this fail.  I went to the following link on Microsoft's website "http://support.microsoft.com/kb/269495/EN-US/" and the value that it says to add to my registry is arleady there.   I am at a loss.  

My connection string is as follows:

Public cn As New OleDbConnection("Provider=vfpoledb.1 ;Data Source=\\server\amw.dbc;Mode=ReadWrite|Share Deny None;Collating Sequence=MACHINE;Password=''")
britttdAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jacobhooverCommented:
Are there any errors in the error collection?  

If so, what are they?
0
britttdAuthor Commented:
How do I look in this?
0
jacobhooverCommented:
           Try
                  Me.Connection.Open()
            Catch e As System.Data.OleDb.OleDbException
                  Dim err As System.Data.OleDb.OleDbError
                  For Each err In e.Errors()
                        System.Diagnostics.Debug.WriteLine(e.Message)
                  Next
            End Try
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

britttdAuthor Commented:
Only error that comes up is:

Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
0
jacobhooverCommented:
Do you have the Visual Fox Pro provider on your new machine?

Also, the call to :
  System.Diagnostics.Debug.WriteLine(e.Message)
will only be seen from inside your debugger.  If you don't have a debugger installed on the "new" machine, you may have to use a different means of showing the error... Ie, creating a messagebox and displaying each of the e.Message in it.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
britttdAuthor Commented:
I ended up reformatting my machine and it works fine now.  Don't know what it was but it works now so...
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Programming

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.