Shamil Salakhetdinov
shamil at users.mns.ru
Tue Jan 10 14:09:02 CST 2006
<<<
it will fail at different points each time.
>>>
Andy,
This means you use the same key presses but different data.
Yes, it's not easy to have "clean hands" tests with MS Access databases and
programs...
But you said you get it crashed always in the same (long) VBA procedure?
Shamil
----- Original Message -----
From: "Andy Lacey" <andy at minstersystems.co.uk>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Tuesday, January 10, 2006 10:40 PM
Subject: Re: [AccessD] Access97 on W2000 crashes
> Thanks for that Shamil I'll try it tomorrow.
>
> I'd have found the code if I thought that feasible I assure you but there
is
> little or no pattern to where it crashes. I can execute the same key
presses
> and it will fail at different points each time.
>
> -- Andy Lacey
> http://www.minstersystems.co.uk
>
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> > Shamil Salakhetdinov
> > Sent: 10 January 2006 18:07
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] Access97 on W2000 crashes
> >
> >
> > > Does any of this give any clues Shamil?
> > No, Andy, it doesn't. :(
> >
> > They look similar despite the difference in fullpath name for
> > outlook - this
> > (hopefully) shouldn't force MS Access to automatically change
> > refs because GUIDs are the same.
> >
> > The problem could be in the differences of the product
> > versions and/or indirectly referenced/loaded DLLs.
> >
> > I did write a small PSAPI.dll based utility, which creates
> > the XML file with the information about DLLs loaded by MS
> > Access directly or indirectly:
> >
> > http://smsconsulting.spb.ru/download/tests/myPSAPI.zip (10KB)
> >
> > Run it on your development PC and on the target PC after you
> > run your test because DLLs are loaded on demand only and you
> > will have the complete list of DLL only when you run your app
> > (Of course on the target system your app should be decompiled
> > and compiled and saved to let it run successfully).
> >
> > You'll get processes.xml file with information like in P.S.
> > of this message. MS Access should be active when you run the utility.
> >
> > When you get two xml files you can compare them to see what
> > are the differences of the loaded DLLs versions.
> >
> > But it still could be no clue there....
> >
> > Andy, there are no miracles in programming, you know that as
> > well as I do - instead of spending time trying to indirectly
> > solve the issue I'd recommend you to find the code lines
> > giving you the trouble - it's the second day you are looking
> > for "magical" solution - IMO it's now time to stop relying on
> > miracles and to do some dirty routine tracing/logging work
> > and fix the bug in your (legacy) code...
> >
> > And when you fix the trouble - use .MDEs they run faster and
> > are smaller in size than big MDBs with compiled and saved code...
> >
> > I'm sorry, I think I can't be of any help further in this issue....
> >
> > Shamil
> >
> > P.S.
> >
> > <?xml version="1.0" encoding="utf-8" ?>
> > - <Processes>
> > - <Process>
> > <Id>3708</Id>
> > <BaseName>msaccess.exe</BaseName>
> > <MemUsage>7,524KB</MemUsage>
> > <ExeFullPath>D:\Program
> > Files\MSOffice\97\Office\msaccess.exe</ExeFullPath>
> > <ModulesCount>25</ModulesCount>
> > - <version>
> > <vi>CompanyName: Microsoft Corporation</vi>
> > <vi>FileDescription: Microsoft Access</vi>
> > <vi>FileVersion: 8.0.5903</vi>
> > <vi>InternalName: MSACCESS</vi>
> > <vi>LegalCopyright: Copyright C Microsoft Corp. 1991-1997.
> > All rights reserved.</vi>
> > <vi>OriginalFilename: MSACCESS.EXE</vi>
> > <vi>ProductName: MicrosoftR Access</vi>
> > <vi>ProductVersion: 8.0.5903</vi>
> > <vi>Comments</vi>
> > <vi>LegalTrademarks</vi>
> > <vi>PrivateBuild</vi>
> > <vi>SpecialBuild</vi>
> > </version>
> > - <Modules>
> > - <Module>
> > <BaseName>ntdll.dll</BaseName>
> > <ExeFullPath>D:\WINDOWS\system32\ntdll.dll</ExeFullPath>
> > - <version>
> > <vi>CompanyName: Microsoft Corporation</vi>
> > <vi>FileDescription: NT Layer DLL</vi>
> > <vi>FileVersion: 5.2.3790.0 (srv03_rtm.030324-2048)</vi>
> > <vi>InternalName: ntdll.dll</vi>
> > <vi>LegalCopyright: C Microsoft Corporation. All rights
> > reserved.</vi>
> > <vi>OriginalFilename: ntdll.dll</vi>
> > <vi>ProductName: MicrosoftR WindowsR Operating System</vi>
> > <vi>ProductVersion: 5.2.3790.0</vi>
> > <vi>Comments</vi>
> > <vi>LegalTrademarks</vi>
> > <vi>PrivateBuild</vi>
> > <vi>SpecialBuild</vi>
> > </version>
> > </Module>
> > - <Module>
> > <BaseName>kernel32.dll</BaseName>
> > <ExeFullPath>D:\WINDOWS\system32\kernel32.dll</ExeFullPath>
> > - <version>
> > <vi>CompanyName: Microsoft Corporation</vi>
> > <vi>FileDescription: Windows NT BASE API Client DLL</vi>
> > <vi>FileVersion: 5.2.3790.0 (srv03_rtm.030324-2048)</vi>
> > <vi>InternalName: kernel32</vi>
> > <vi>LegalCopyright: C Microsoft Corporation. All rights
> > reserved.</vi>
> > <vi>OriginalFilename: kernel32</vi>
> > <vi>ProductName: MicrosoftR WindowsR Operating System</vi>
> > <vi>ProductVersion: 5.2.3790.0</vi>
> >
> >
> > ... etc...
> >
> > P.P.S (could be of help in other issues)
> >
> > If you run myPSAPI.exe with a parameter equal to a (part of
> > the) name of an active process/processes it will create
> > processes.xml file for this process/these processes....
> >
> > ----- Original Message -----
> > From: "Andy Lacey" <andy at minstersystems.co.uk>
> > To: "Access Developers discussion and problem solving"
> > <accessd at databaseadvisors.com>
> > Sent: Tuesday, January 10, 2006 4:52 PM
> > Subject: Re: [AccessD] Access97 on W2000 crashes
> >
> >
> > > I've listed below the results of running ListRefs on the
> > two machines.
> > > At first I thought they were identical, but there is one
> > difference in
> > > the
> > path
> > > to the Outlok library. Under W98 this is
> > >
> > > C:\PROGRAM FILES\MICROSOFT OFFICE\OFFICE\msoutl9.olb
> > >
> > > whereas W2K has the old-fashioned DOS'y path of
> > >
> > > C:\PROGRA~1\MICROS~1\Office\msoutl9.olb
> > >
> > > Surely this is not significant. It can't be, can it?
> > >
> > > The other thing I thought odd was that the DAO 3.5
> > reference returns a
> > > .Major and .Minor of 4.0 not 3.5, but then again it's the
> > same on both
> > > machines.
> > >
> > >
> > > Windows 98
> > > ==========
> > > VBA.3.0 0 True False
> > > C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\VBA\VBA332.DLL
> > > {000204EF-0000-0000-C000-000000000046}
> > > False
> > > Access.8.0 0 True False
> > > C:\Program Files\Microsoft Office\Office\MSACC8.OLB
> > > {4AFFC9A0-5F99-101B-AF4E-00AA003F0F07}
> > > False
> > > DAO.4.0 0 False False
> > > C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\DAO\DAO350.DLL
> > > {00025E01-0000-0000-C000-000000000046}
> > > False
> > > Outlook.9.0 0 False False
> > > C:\PROGRAM FILES\MICROSOFT OFFICE\OFFICE\msoutl9.olb
> > > {00062FFF-0000-0000-C000-000000000046}
> > > False
> > > Word.8.0 0 False False
> > > C:\Program Files\Microsoft Office\Office\MSWORD8.OLB
> > > {00020905-0000-0000-C000-000000000046}
> > > False
> > >
> > >
> > > Windows 2000
> > > ============
> > > VBA.3.0 0 True False
> > > C:\Program Files\Common Files\Microsoft Shared\VBA\VBA332.DLL
> > > {000204EF-0000-0000-C000-000000000046}
> > > False
> > > Access.8.0 0 True False
> > > C:\Program Files\Microsoft Office\Office\msacc8.olb
> > > {4AFFC9A0-5F99-101B-AF4E-00AA003F0F07}
> > > False
> > > DAO.4.0 0 False False
> > > C:\Program Files\Common Files\Microsoft Shared\DAO\dao350.dll
> > > {00025E01-0000-0000-C000-000000000046}
> > > False
> > > Outlook.9.0 0 False False C:\PROGRA~1\MICROS~1\Office\msoutl9.olb
> > > {00062FFF-0000-0000-C000-000000000046}
> > > False
> > > Word.8.0 0 False False
> > > C:\Program Files\Microsoft Office\Office\MSWORD8.OLB
> > > {00020905-0000-0000-C000-000000000046}
> > > False
> > >
> > >
> > > Does any of this give any clues Shamil?
> > >
> > >
> > > --
> > > Andy Lacey
> > > http://www.minstersystems.co.uk
> > >
> > >
> > >
> > <<< tail skipped>>>
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com