Installing Visual Basic 6 "downgraded" Jet 4.0 to Jet 3.5. How to fix?

[bjhartin]

All,

I was working at a client's site when I installed Visual Basic 6 on a
machine at their request. Existing applications on this machine had
specified version 4.0 of the Jet OLEDB provider in a data source string
in their config files. After installing VB 6, they stopped working,
producing the error "3220: The supplied provider is different from the
one already in use. Changing their configuration files to specify
version 3.5.1 fixes the problem.

I would prefer the machine to be at version 4.0 of Jet. Any ideas? I
have tried the following:

1. Installing the latest MDAC update.
2. Installing the latest Jet 4.0 service pack.
3. Installing service pack 6 for Visual Studio.
4. Uninstalling Visual Basic 6.0's Jet component/option.
5. Uninstalling Visual Basic 6.0 altogether.

None of these seem to have had any effect. Does anyone know how to
"re-upgrade" this machine so that the 4.0 Jet engine is available?

Thanks,

Brian

[Matt Williamson]

Brian-

This should help. I went through this as well.

http://support.microsoft.com/default...b;en-us;271908

-HTH

Matt

<bj******@yahoo.com> wrote in message
news:11*********************@f14g2000cwb.googlegro ups.com...

All,

I was working at a client's site when I installed Visual Basic 6 on a
machine at their request. Existing applications on this machine had
specified version 4.0 of the Jet OLEDB provider in a data source string
in their config files. After installing VB 6, they stopped working,
producing the error "3220: The supplied provider is different from the
one already in use. Changing their configuration files to specify
version 3.5.1 fixes the problem.

I would prefer the machine to be at version 4.0 of Jet. Any ideas? I
have tried the following:

1. Installing the latest MDAC update.
2. Installing the latest Jet 4.0 service pack.
3. Installing service pack 6 for Visual Studio.
4. Uninstalling Visual Basic 6.0's Jet component/option.
5. Uninstalling Visual Basic 6.0 altogether.

None of these seem to have had any effect. Does anyone know how to
"re-upgrade" this machine so that the 4.0 Jet engine is available?

Thanks,

Brian

[Paul Clement]

On 31 Oct 2005 10:25:36 -0800, bj******@yahoo.com wrote:

¤ All,
¤
¤ I was working at a client's site when I installed Visual Basic 6 on a
¤ machine at their request. Existing applications on this machine had
¤ specified version 4.0 of the Jet OLEDB provider in a data source string
¤ in their config files. After installing VB 6, they stopped working,
¤ producing the error "3220: The supplied provider is different from the
¤ one already in use. Changing their configuration files to specify
¤ version 3.5.1 fixes the problem.
¤
¤ I would prefer the machine to be at version 4.0 of Jet. Any ideas? I
¤ have tried the following:
¤
¤ 1. Installing the latest MDAC update.
¤ 2. Installing the latest Jet 4.0 service pack.
¤ 3. Installing service pack 6 for Visual Studio.
¤ 4. Uninstalling Visual Basic 6.0's Jet component/option.
¤ 5. Uninstalling Visual Basic 6.0 altogether.
¤
¤ None of these seem to have had any effect. Does anyone know how to
¤ "re-upgrade" this machine so that the 4.0 Jet engine is available?

Is this happening to a DataEnvironment class? If so the RunPromptBehavior of the Connection object
should be set to adPromptNever.
Paul
~~~~
Microsoft MVP (Visual Basic)

[bjhartin]

I did try downloading the latest MDAC, then running the Jet 4.0 SP 8
install. That didn't seem to help, although I'll try again using the
exact set of steps that they specify.

Thanks.

[bjhartin]

Yes, I believe I did use the DataEnvironment on this project (it's been
a long time since I wrote the code). However, it worked fine under Jet
4.0 prior to installing VB 6, and it works fine under Jet 3.5.1 after
installing VB 6.0, just not under 4.0 after installing VB 6.

Why would changing this property help? I'll try it when I return to
their site, but I'm curious as to why this would help.

[Ralph]

<bj******@yahoo.com> wrote in message
news:11**********************@g43g2000cwa.googlegr oups.com...

Yes, I believe I did use the DataEnvironment on this project (it's been
a long time since I wrote the code). However, it worked fine under Jet
4.0 prior to installing VB 6, and it works fine under Jet 3.5.1 after
installing VB 6.0, just not under 4.0 after installing VB 6.

Why would changing this property help? I'll try it when I return to
their site, but I'm curious as to why this would help.

I am curious too.

I think it basically forces the program to ignore the warning and go on to
use the 'other' provider.

Are you also using DAO? Some DAO controls need to have DAO 3.51 installed as
well. It comes with the Jet 4 packages but is not often registered
correctly.

-ralph

[bjhartin]

I don't think that could be an issue for me since this code runs fine
on a fresh Windows 2000 box that does not have Jet 3.5.1 on it, as long
as I specify the 4.0 version of the Jet OLEDB provided in the config
file for the application.

[Ken Halter]

<bj******@yahoo.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...

I don't think that could be an issue for me since this code runs fine
on a fresh Windows 2000 box that does not have Jet 3.5.1 on it, as long
as I specify the 4.0 version of the Jet OLEDB provided in the config
file for the application.

Any VB controls that support Databinding, are based on Jet 3.51... VB itself
installs the required support. Jet engines > 3.51 need to be installed. MDAC
and Jet 4 are separate downloads these days (from what I gather, poking
around the groups)

If you install VB on a fresh OS, create databases using only VB methods,
open that in Access > 97 and accept Access's desire to "upgrade" the DB, the
vb controls will no longer be able to read that database (without, if
supported, changing property settings on the controls you're using)

fwiw, I have the whole shabang installed and can pick between them.... no
problem. With ADO/DAO, you can even "mix and match" if you love punishment
<g> Just specify the library when declaring variables.

Private Sub Form_Load()
Dim oADO_RS As ADODB.Recordset
Dim oJet_RS As DAO.Recordset
End Sub


--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm
Please keep all discussions in the groups..

[Ralph]

<bj******@yahoo.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...

I don't think that could be an issue for me since this code runs fine
on a fresh Windows 2000 box that does not have Jet 3.5.1 on it, as long
as I specify the 4.0 version of the Jet OLEDB provided in the config
file for the application.

You misunderstood me.
If you look carefully you will find the following dll located and registered
on your "Jet 4" Win2k machine:
<Drive:>\Program Files\Common Files\Microsoft Shared\Dao\Dao350.dll

I am not talking about the Jet Engine, drivers, providers, or the Data
Access Library you are using, merely the dependency of 'Data Bound' controls
on this DLL. Subsequently any controls you are using in your application may
have a dependency on this component as well. (Even though it may not appear
within your references.)

This may not actually be a problem in your case. I only brought it up
because it has caused problems for others in a similar situation. While
later "Jet" service packs install the dll, it doesn't always register the
dll correctly. It will take you less than a minute to locate the dll and
register it on the target machine....

[Regsvr32.exe /U
"<Drive:>\Program Files\Common Files\Microsoft Shared\Dao\Dao350.dll"
Regsvr32.exe
"<Drive:>\Program Files\Common Files\Microsoft Shared\Dao\Dao350.dll"
]

It might fix the problem.

-ralph

[Larry Linson]

IIRC, SP 3 or 4 for VB6 "upgraded" VB6 to use Jet 4.0 instead of Jet 3.51.
If SP 6 is a "cumulative" SP, including all previous SPs, I would expect
that to do the upgrade, as well.

Larry Linson
Microsoft Access MVP
<bj******@yahoo.com> wrote in message
news:11*********************@f14g2000cwb.googlegro ups.com...

All,

I was working at a client's site when I installed Visual Basic 6 on a
machine at their request. Existing applications on this machine had
specified version 4.0 of the Jet OLEDB provider in a data source string
in their config files. After installing VB 6, they stopped working,
producing the error "3220: The supplied provider is different from the
one already in use. Changing their configuration files to specify
version 3.5.1 fixes the problem.

I would prefer the machine to be at version 4.0 of Jet. Any ideas? I
have tried the following:

1. Installing the latest MDAC update.
2. Installing the latest Jet 4.0 service pack.
3. Installing service pack 6 for Visual Studio.
4. Uninstalling Visual Basic 6.0's Jet component/option.
5. Uninstalling Visual Basic 6.0 altogether.

None of these seem to have had any effect. Does anyone know how to
"re-upgrade" this machine so that the 4.0 Jet engine is available?

Thanks,

Brian

[Paul Clement]

On 31 Oct 2005 12:46:15 -0800, bj******@yahoo.com wrote:

¤ Yes, I believe I did use the DataEnvironment on this project (it's been
¤ a long time since I wrote the code). However, it worked fine under Jet
¤ 4.0 prior to installing VB 6, and it works fine under Jet 3.5.1 after
¤ installing VB 6.0, just not under 4.0 after installing VB 6.
¤
¤ Why would changing this property help? I'll try it when I return to
¤ their site, but I'm curious as to why this would help.

The DataEnvironment can be somewhat quirky and I've seen instances where this fixed the problem.
From a technical standpoint I can't explain why.

Something is causing the version of the provider to change at runtime and that is likely the reason
you are getting the specified error.
Paul
~~~~
Microsoft MVP (Visual Basic)

[Ralph]

"Paul Clement" <Us***********************@swspectrum.com> wrote in message
news:kr********************************@4ax.com...

On 31 Oct 2005 12:46:15 -0800, bj******@yahoo.com wrote:

¤ Yes, I believe I did use the DataEnvironment on this project (it's been
¤ a long time since I wrote the code). However, it worked fine under Jet
¤ 4.0 prior to installing VB 6, and it works fine under Jet 3.5.1 after
¤ installing VB 6.0, just not under 4.0 after installing VB 6.
¤
¤ Why would changing this property help? I'll try it when I return to
¤ their site, but I'm curious as to why this would help.

The DataEnvironment can be somewhat quirky and I've seen instances where this fixed the problem. From a technical standpoint I can't explain why.

Something is causing the version of the provider to change at runtime and that is likely the reason you are getting the specified error.
Paul
~~~~
Microsoft MVP (Visual Basic)

I had noticed the same phenomena, but often forget about it unless trouble
happens then just toggle it as a matter of habit. In this case it turned out
to be a licensing issue - "the other 429 Error".

I didn't think of it because usually a 429 caused by a missing license
reports itself as such. Apparently that doesn't happen with Win98/MSAccess
98. Useful to know.

Glad the OP came back and reported the 'fix'.

-ralph

[bjhartin]

I'll try this when I return to the client site. When I have a fix,
I'll be sure to post it.

For clarity, here's a table of situations and how the app behaves:

Environment: Clean PC with Jet 3.5.1
Config File: Jet 3.5.1 specified
Result: No problem

Environment: Clean PC with Jet 3.5.1
Config File: Jet 4.0 specified
Result: Failure: "provider not found" (as expected)

Environment: Clean PC with Jet 4.0
Config File: Jet 3.5.1 specified
Result: Failure: "provider not found" (as expected)

Environment: Clean PC with Jet 4.0
Config File: Jet 4.0 specified
Result: Failure: No problem

Environment: Clean PC with Jet 4.0, after installation of VB 6 and
service pack 6
Config File: Jet 3.5.1 specified
Result: Failure: No problem (UNEXPECTED - I would have thought that
this would fail)

Environment: Clean PC with Jet 4.0, after installation of VB 6
Config File: Jet 4.0 specified
Result: Failure: 3220 "supplied provider is different from the one
already in use" (UNEXPECTED)

Environment: Clean PC with Jet 4.0, after installation of VB 6, then VB
Service Pack 6
Config File: Jet 4.0 specified
Result: Failure: 3220 "supplied provider is different from the one
already in use" (UNEXPECTED)

Environment: Clean PC with Jet 4.0, after installation of VB 6, then VB
Service Pack 6, then MDAC 2.8
Config File: Jet 4.0 specified
Result: Failure: 3220 "supplied provider is different from the one
already in use" (UNEXPECTED)

Environment: Clean PC with Jet 4.0, after installation of VB 6, then VB
Service Pack 6, then MDAC 2.8, then Jet 4.0 sp8
Config File: Jet 4.0 specified
Result: Failure: 3220 "supplied provider is different from the one
already in use" (UNEXPECTED)

[bjhartin]

That's what I thought, too, but it didn't seem to solve the problem.