MDAC, Jet, and XP

[Darryl Kerkeslager]

Okay, so the Jet support is no longer in MDAC as of a few years ago. This
was not a problem previously, as MDAC 2.5 was included with Windows 2000.
Now, however, Windows XP does not include MDAC 2.5.

(Right so far?)

So, if our IT people who are installing XP Pro on all new computers, decide
that they do not want to allow Jet40SP3_Comp.exe to be installed, does that
mean this statement will not work. period, end of story?

Dim cat As New ADOX.Catalog
cat.Create "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=my.mdb"
Darryl Kerkeslager

[Tom van Stiphout]

On Mon, 17 Jan 2005 14:04:01 -0500, "Darryl Kerkeslager"
<Ke*********@comcast.net> wrote:

Comments in-line.
-Tom.

Okay, so the Jet support is no longer in MDAC as of a few years ago. This
was not a problem previously, as MDAC 2.5 was included with Windows 2000.
Now, however, Windows XP does not include MDAC 2.5.

(Right so far?) You can still create objects of type ADODB.Connection.2.5 etcetera.
Newer versions of ADO appear to include the older objects.

So, if our IT people who are installing XP Pro on all new computers, decide
that they do not want to allow Jet40SP3_Comp.exe to be installed, does that
mean this statement will not work. period, end of story? IT will install the software needed to run the company's applications.
IT is in a subservient role to the organization as a whole.

Dim cat As New ADOX.Catalog
cat.Create "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=my.mdb" Try it on the machine you described above, and report your findings.


Darryl Kerkeslager

[Trevor Best]

Tom van Stiphout wrote:

IT is in a subservient role to the organization as a whole.

Except that they usually consider themselves gods and will advise
management that the old sofware is a security risk so they won't have to
do any work and get down to the real business of finishing Half Life 2.

--
This sig left intentionally blank

[Darryl Kerkeslager]

So far the response to most issues has been that "Access will not be
supported", which has been interpreted several ways.
Darryl Kerkeslager

"Trevor Best" <no****@besty.org.uk> wrote

Tom van Stiphout wrote:

IT is in a subservient role to the organization as a whole.

Except that they usually consider themselves gods and will advise
management that the old sofware is a security risk

[Darryl Kerkeslager]

"Tom van Stiphout" <no*************@cox.net> wrote:

"Darryl Kerkeslager" <Ke*********@comcast.net> wrote:

Okay, so the Jet support is no longer in MDAC as of a few years ago. Thiswas not a problem previously, as MDAC 2.5 was included with Windows 2000.
Now, however, Windows XP does not include MDAC 2.5.

You can still create objects of type ADODB.Connection.2.5 etcetera.
Newer versions of ADO appear to include the older objects. Dim cat As New ADOX.Catalog
cat.Create "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=my.mdb"

Try it on the machine you described above, and report your findings.

Well, the test was only perhaps half-valid. I was only able to test it on a
XP Pro machine that had been upgraded from Windows 2000 - not a clean
install of XP Pro. So I'm not sure, still. But the code did work on that
machine. My concern is that a new machine, with XP PRo and Office 2003 will
not run the above. But unless someone has such a setup (we won't get a
clean install for awhile, unless a hard drive crashes [no wait, I have an
idea..]), I guess I won't know.
Darryl Kerkeslager