Microsoft Data Access SDK 
Author Message
 Microsoft Data Access SDK

I know this isn't specifically a VB issue, but I suspect there are many on
the NG that are familiar with these matters.

I spent about two hours last night trying to install the current MS Data
Access SDK to the following path on my home pc:

e:\program files\msdasdk

All went well while the files were being copied, but in the final phase of
the install there are apparently numerous registry updates. Every time I
tried to do this install I would get a fatal error in a dll and the install
would terminate.

I finally resorted to allowing the sdk to install to the default directory
c:\msdasdk. When I did that everything worked without a hitch. I then moved
the entire directory to the path shown above and used Norton Utilities
Windocter to find all of the registry keys that had to be upfixed.

My question is, what would cause this type of error? I am guessing that it
may have something to do with the overall length of the full path to a
particular file. If that is so, then is it absolutely certain beyond any
doubt that I will run into problems when I start using the sdk because the
path is too long?

BTW, I'm using Win95 OSR1 with all appropriate service packs and other
patches and my file system is FAT16.



Fri, 10 May 2002 03:00:00 GMT  
 Microsoft Data Access SDK
I had no problems installing the MDAC 2.1.2.4202.3 (GA) download from a
non-default location i.e.

    D:\Program Files\mssdk

Peter



Quote:
> I know this isn't specifically a VB issue, but I suspect there are many on
> the NG that are familiar with these matters.

> I spent about two hours last night trying to install the current MS Data
> Access SDK to the following path on my home pc:

> e:\program files\msdasdk

> All went well while the files were being copied, but in the final phase of
> the install there are apparently numerous registry updates. Every time I
> tried to do this install I would get a fatal error in a dll and the
install
> would terminate.

> I finally resorted to allowing the sdk to install to the default directory
> c:\msdasdk. When I did that everything worked without a hitch. I then
moved
> the entire directory to the path shown above and used Norton Utilities
> Windocter to find all of the registry keys that had to be upfixed.

> My question is, what would cause this type of error? I am guessing that it
> may have something to do with the overall length of the full path to a
> particular file. If that is so, then is it absolutely certain beyond any
> doubt that I will run into problems when I start using the sdk because the
> path is too long?

> BTW, I'm using Win95 OSR1 with all appropriate service packs and other
> patches and my file system is FAT16.



Fri, 10 May 2002 03:00:00 GMT  
 Microsoft Data Access SDK

Quote:

> I had no problems installing the MDAC 2.1.2.4202.3 (GA) download from a
> non-default location i.e.

>     D:\Program Files\mssdk

Hmmmm. Curious. Any guesses as to what might be causing the problem I
described?


Fri, 10 May 2002 03:00:00 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. ADO Data Control in Visual Basic 5 with Microsoft Data Access SDK 2.0

2. Announcement: Excel Addin and SDK simplifies access to Microsoft OLAP Server

3. microsoft access version 7 - data access object problem

4. access Microsoft Outlook from Microsoft Access

5. Programming with Microsoft Speech SDK

6. Anyone used the Microsoft Speech SDK ?

7. microsoft xtel.dll (SAPI SDK)

8. Microsoft Active Movie SDK

9. ADSI 2.5 Microsoft Platform SDK sample problems

10. The Microsoft SDK documentation

11. SPY utility provided with the Microsoft Windows Software Development Kit (SDK)

 

 
Powered by phpBB® Forum Software