(1)
With Access2000 (on Win98), PDW build produced following BOOTSTRAP section in SETUP.LST
Used DAO in app.
[Bootstrap Files]
File1=@msvbvm50.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,5/11/98 8:01:00 PM,1355776,5.1.43.19
File2=@ODESTKIT.DLL,$(WinSysPathSysFile),,,11/3/98 12:00:00 AM,101888,6.0.82.67
File3=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,11/3/98 12:00:00 AM,22288,4.71.1460.1
File4=@STDOLE2.TLB,$(WinSysPathSysFile),$(TLBRegister),,3/8/99 12:00:00 AM,17920,2.40.4275.1
File5=@asycfilt.dll,$(WinSysPathSysFile),,,4/24/00 10:01:30 AM,147728,2.40.4275.1
File6=@olepro32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,3/8/99 12:00:00 AM,164112,5.0.4275.1
File7=@OLEAUT32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,4/24/00 10:01:34 AM,598288,2.40.4275.1
File8=@msvbvm60.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,12/9/98 4:28:18 PM,1409024,6.0.82.68
With this OLD build the app installs flawlessly on XP
(2)
With passage of time, Access2000 now on XP development machine, same package is built with PDW,
with PDW, but now gives the following [BOOTSTRAP]
Used ADO in app.
[Bootstrap Files]
File1=@msvbvm50.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8/18/01 12:00:00 PM,1355776,5.2.82.44
File2=@ODESTKIT.DLL,$(WinSysPathSysFile),,,11/3/98 12:00:00 AM,101888,6.0.82.67
File3=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,11/3/98 12:00:00 AM,22288,4.71.1460.1
File4=@stdole2.tlb,$(WinSysPathSysFile),$(TLBRegister),,8/18/01 12:00:00 PM,17920,3.50.5014.0
File5=@asycfilt.dll,$(WinSysPathSysFile),,,8/18/01 12:00:00 PM,77824,3.50.5014.0
File6=@olepro32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8/18/01 12:00:00 PM,106496,5.0.5014.0
File7=@oleaut32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8/29/02 3:41:10 AM,569344,3.50.5016.0
With this NEW build, the app installs (shakily, you have to ignore message saying that
MSCOMCTL.OCX could not be copied because it was in use),
- and then will not connect to the DB on the install (XP) PC.
- but paradoxically it WILL connect to an identical DB on development (XP) PC.
Does anyone out there have an "Oh yes - I know that old problem"?
I hope so!
Have struggled with it for some time (checked MDAC, applied SR-1 to Office 2000...)
and it's urgent.
(PS: not sure if the BOOTSTRAP information provided above is relevant - but included it to be as complete as poss).
Many thanks
With Access2000 (on Win98), PDW build produced following BOOTSTRAP section in SETUP.LST
Used DAO in app.
[Bootstrap Files]
File1=@msvbvm50.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,5/11/98 8:01:00 PM,1355776,5.1.43.19
File2=@ODESTKIT.DLL,$(WinSysPathSysFile),,,11/3/98 12:00:00 AM,101888,6.0.82.67
File3=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,11/3/98 12:00:00 AM,22288,4.71.1460.1
File4=@STDOLE2.TLB,$(WinSysPathSysFile),$(TLBRegister),,3/8/99 12:00:00 AM,17920,2.40.4275.1
File5=@asycfilt.dll,$(WinSysPathSysFile),,,4/24/00 10:01:30 AM,147728,2.40.4275.1
File6=@olepro32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,3/8/99 12:00:00 AM,164112,5.0.4275.1
File7=@OLEAUT32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,4/24/00 10:01:34 AM,598288,2.40.4275.1
File8=@msvbvm60.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,12/9/98 4:28:18 PM,1409024,6.0.82.68
With this OLD build the app installs flawlessly on XP
(2)
With passage of time, Access2000 now on XP development machine, same package is built with PDW,
with PDW, but now gives the following [BOOTSTRAP]
Used ADO in app.
[Bootstrap Files]
File1=@msvbvm50.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8/18/01 12:00:00 PM,1355776,5.2.82.44
File2=@ODESTKIT.DLL,$(WinSysPathSysFile),,,11/3/98 12:00:00 AM,101888,6.0.82.67
File3=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,11/3/98 12:00:00 AM,22288,4.71.1460.1
File4=@stdole2.tlb,$(WinSysPathSysFile),$(TLBRegister),,8/18/01 12:00:00 PM,17920,3.50.5014.0
File5=@asycfilt.dll,$(WinSysPathSysFile),,,8/18/01 12:00:00 PM,77824,3.50.5014.0
File6=@olepro32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8/18/01 12:00:00 PM,106496,5.0.5014.0
File7=@oleaut32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,8/29/02 3:41:10 AM,569344,3.50.5016.0
With this NEW build, the app installs (shakily, you have to ignore message saying that
MSCOMCTL.OCX could not be copied because it was in use),
- and then will not connect to the DB on the install (XP) PC.
- but paradoxically it WILL connect to an identical DB on development (XP) PC.
Does anyone out there have an "Oh yes - I know that old problem"?
I hope so!
Have struggled with it for some time (checked MDAC, applied SR-1 to Office 2000...)
and it's urgent.
(PS: not sure if the BOOTSTRAP information provided above is relevant - but included it to be as complete as poss).
Many thanks