JRO (Jet Replication Object) / MDAC

[Chad123]

Hey,

I am having a HUGE issue... When I use MDAC 2.5 I get the Jet connection to work, but the JRO dll cannot be found. I have tried several different MDAC install files, even one off Microsofts site - same thing...

Now, when I install MDAC 2.6 or higher (regardless of whether it is overtop of v2.5 or fresh) I get the JRO to work properlly, but then I can't get the Jet connection to work.

Is there a way I can install MDAC 2.6 with Jet?

Any ideas of how I can get this to work would be greatly appreciated.

Thanks,
Chad

 

[dilettante]

I have to wonder about the future of Jet.

As of MDAC 2.6 Jet was split out as a separate download.

Apparently, as of Jet 4.0 SP 5, JRO isn't even included with the Jet 4.0 package anymore.

Currently at this link:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;239114

You can get Jet 4.0 SP 7, which comes in flavors tailored to various Windows OS versions.

I saw something suggesting that Jet 4.0 SP 3 was available and still had JRO, but following the download link I was met with "Jet 4.0 SP3 has been retired. If you're looking for SP3, download and install SP7."

I really doubt that MDAC 2.6 is providing you with JRO. I wonder if you have ended up with an incompatible set of data access components from various packages and release levels?

Anybody know what's going on with Jet and JRO?

Anyone else want to take a stab at explaining the symptoms above?

 

[Chad123]

I tried all of the above and I kept seeing the same symptoms.

Thusly, I removed all versions of MDAC and Jet, rebooted (Being a Win9x environment), then reinstalled MDAC 2.5 sp3, which contails Jet, and JRO... This seemed to help as everything is working now...

However, Any other suggestions or updates on the status of JRO and Jet would be great.

Thanks Dilettante

 

[dilettante]

I'm not sure what Microsoft is trying to do with/to Jet. I know they have announced Jet is frozen at 4.0, but then what?

I can't imagine how you'd straighten things out as above on an OS later than Win XP. I'm not sure you can install MDAC 2.5 on Win 2003 Server for example, but perhaps you can.


On the one hand, I tend to be suspicious that this is part of a strategy to kill off both VB and VBScript and force everyone to .Net technologies. I'm not so clear regarding Access.

But on the other hand, what do they expect people developing desktop software to do for a database even if they are programming in VB.Net or C#? MSDE can't really be the answer here, can it? Suddenly even for small multiuser applications you have to run a database server, unlike with Jet where a simple file server was adequate when your needs were modest.

I'm missing something here, I know it. Can anybody enlighten me?