Yes, please do contact your local support subsidiary/team for further
assistance.
It's possible that your issue (and others in this
thread) may need to be reproduced in order for us to resolve the problem.
And, we may need ODBC traces and such. As this complex an issue is
*extremely* difficult (not to mention not very timely) to resolve in the
newsgroups, I'd recommend that
you (and others with this problem) contact Microsoft Product Support
Services via telephone so that a dedicated Support Professional can assist
with your request. Please be advised that contacting phone support will be
a charged call. However, if you are simply requesting a hotfix be sent to
you and no other support then charges are usually refunded or waived.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see
http://support.microsoft.com for
regional support phone numbers.
Sincerely,
Rita Nikas, MCSE MCDBA
Product Support Services
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Subject: Re: Jet 4.0 Service Pack 7 does not work with my ODBC driver
| Date: Thu, 10 Jul 2003 13:42:26 -0700
|
| Hi Rita,
|
|
|
| We develop generic ODBC (2.5) driver for database venders. After install
Jet
| 4.0 SP7, MS access can no longer link to tables in our customer database
| through our ODBC 2.5 driver. This has never happened before we install
| Jet4.0 SP7.
|
|
|
| And I have also just learned that Jet4 SP7 does not work well with
| Oracl8.7.1.x ODBC driver. Please take a look at the following discuss
| between me and another developer who is using Oracle ODBC driver:
|
|
|
| note: the Jet4.0 SP7 comes with Windows 2000 SP4 too.
|
|
|
| >We have just upgraded our development machines to Microsoft Windows 2000
| >service pack 4 and noticed that our ODBC driver can no longer open tables
| in
| >Microsoft Access 2000 or 97. This occurs when adding a "linked" and
| >"imported" ODBC table. the error message is "Invalid argument"
| >Just wondering if anyone encountered this problem?
| >Lu
|
|
| > > I head it was a known problem with that SP4.
| > > You had better consider a rollback prior to the SP4 installation.
|
| > >I was having the same issue with Oracle 8.1.7.4, but after
| > >uninstalling SP4 and reinstalling SP4 the issue had disappeared.
| > >"donald ponzini" <
[email protected]>
|
| I think, i should contact you support team.
|
|
|
| Lu
|
|
|
|
| | > Hi Lu.
| >
| > I have a few suggestions and recommendations for you, and some
| explanation.
| >
| > As far as Microsoft Access 97 having issues after installing Jet 4.0
SP7,
| > Microsoft Access 97 doesn't use Jet 4.0 at all - it uses Jet 3.5. So,
I'm
| > thinking *that* piece of the puzzle relates to an old issue where the
ODBC
| > driver gets overwritten, and one can rollback to the Jet 3.5 version of
| the
| > ODBC driver - 237575 comes to mind. And, 237575 has a couple of pointers
| to
| > a couple of other KBs.
| >
| > 237575
| > ACC2000: Reverting to the Access 97 ODBC Driver After Installing MDAC
| >
http://support.microsoft.com/default.aspx?scid=KB;EN-US;237575
| >
| > Since Microsoft Access and Jet don't need an ODBC driver to talk to
| > themselves, the next question I have is: whose ODBC driver are you
using?
| > (Agreeing with Klaus that we *definitely* need more information to try
and
| > help resolve this problem).
| >
| > It's possible that your issue (and others in this thread) may need to be
| > reproduced in order for us to resolve the problem. And, we may need ODBC
| > traces and such. As this complex an issue is *extremely* difficult (not
to
| > mention not very timely) to resolve in the newsgroups, I'd recommend
that
| > you (and others with this problem) contact Microsoft Product Support
| > Services via telephone so that a dedicated Support Professional can
assist
| > with your request. Please be advised that contacting phone support will
be
| > a charged call. However, if you are simply requesting a hotfix be sent
to
| > you and no other support then charges are usually refunded or waived.
| >
| > To obtain the phone numbers for specific technology request please take
a
| > look at the web site listed below.
| >
| >
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
| >
| > If you are outside the US please see
http://support.microsoft.com for
| > regional support phone numbers.
| >
| > Sincerely,
| >
| > Rita Nikas, MCSE MCDBA
| > Product Support Services
| > Microsoft Corporation
| >
| > This posting is provided "AS IS" with no warranties, and confers no
| rights.
| >
| >
| > --------------------
| > | Subject: Jet 4.0 Service Pack 7 does not work with my ODBC driver
| > | Date: Tue, 8 Jul 2003 16:34:10 -0700
| > |
| > | We have just upgraded our development machines to Jet 4.0
| > | SP7 and noticed that our ODBC driver can no longer open
| > | tables in Microsoft Access 2000 or 97. This occurs when
| > | adding a "linked" and "imported" ODBC table. the error
| > | message is "Invalid argument"
| > |
| > | Just wondering if anyone encountered this problem?
| > |
| > | Lu
| > |
| >
|
|
|
