Win XP & MDAC

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Herb - 24 May 2006 18:43 GMT

I have switched from Win2K SP4 to WinXP SP2 and installed VS 2005.

Since then, my VS 6.0 VB projects using the ADO data controls run VERY
slowly. Also, when compiled they will not run on pre-XP machines.

Is this a known issue? Can someone point me in the right direction?

Reply to this Message

Kevin Yu [MSFT] - 25 May 2006 03:57 GMT

Hi,

What database is your app connecting to? Have you applied all patches using
windows update? You can also install the latest version of MDAC 2.8 sp1.
You can download from here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-
a9e0-3a1afbd5922e&DisplayLang=en

Kevin Yu
Microsoft Online Community Support

============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Reply to this Message

Herb - 25 May 2006 12:29 GMT

I am connecting to SQL Server 7 (7.00.1094).

When I compile the program under XPPro SP2, VS6 SP6, and I run it under
Win2K SP4 the actual error that I get is "Error in loading DLL" (number 48).
This occurs as soon as the code hits the first reference to the ADO Data
Control (ver6 SP6)

When I run it on the development machine, the ADO control works, but it is
extremely slow.

The actual reference in the VB app is to msado27.tlb. The Win2K machines are
running MDAC 2.8. When I tried to install MDAC_TYP 2.8 on XPPro SP2, it tells
me "Fatal Setup Error" - "This setup does not support installing on this
operating system"

Thanks

> Hi,
>
[quoted text clipped - 17 lines]
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)

Reply to this Message

Kevin Yu [MSFT] - 26 May 2006 04:05 GMT

Hi,

If you're using ADODC, you have to ship msadodc.ocx with your app. It's
under c:\windows\system32\msadodc.ocx. Since it's a COM object, when copied
to another machine, you also have to register it with regsvr32.exe.

Kevin Yu
Microsoft Online Community Support

============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Reply to this Message

Herb - 26 May 2006 12:41 GMT

Using Component Checker I found that several MDAC files on the client machine
were the wrong version. I copied these from the development machine, and now
ADO works.

> Hi,
>
[quoted text clipped - 14 lines]
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)

Reply to this Message

Kevin Yu [MSFT] - 29 May 2006 04:02 GMT

It was nice to hear that you have had the problem resolved.

Thanks for sharing your experience with all the people here. If you have
any questions, please feel free to post them in the community.

Kevin Yu
Microsoft Online Community Support

============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Reply to this Message

VB Forum / Database Access / May 2006

Win XP & MDAC