Subject: | |
From: | |
Reply To: | |
Date: | Fri, 13 Feb 1998 21:30:14 GMT |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
I experienced something like that. First, I never had problems with
ODBCLink/32 on WinNT 4.0. Second, on few Win95 occurences I had the
following message when I tried to setup a ODBClink/32 DSN:
"Setup could not load ... You may be low on virtual memory" and blablabla.
I finally found out that someone, something or some witch, when installing
some software (related to odbc I guess) replaced the CTL3D32.dll with a
wrong version. The problem was resolved after replacing manually the bad
one with the one provided with ODBCLink/32 (CTL3D95.dll). Up to now, this
manual fix did not bring other problem.
--
Michel Gauthier
[log in to unmask]
Produits Forestiers Donohue Inc.
The ideas expressed/language used reflect those of the author,
Not necessarly those of Donohue Inc.
Brian Manley <[log in to unmask]> wrote in article
<01BD3619.7F124CF0@IP_IS_125>...
Hey all...
I have another ODBCLink/SE-32 problem.
When installing on WinNT 4.0 workstation, everything works fine. But on a
Win95 machine (OSR2), I get the following when trying to create a DSN with
the ODBC applet in Control Panel:
"The setup routines for the ODBCLink/SE-32 Driver ODBC driver could not be
loaded due to system error code 1157"
|
|
|