Re: access crashes every time I do this

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: carylrahn (carylrahn_at_discussions.microsoft.com)
Date: 09/25/04 

Date: Fri, 24 Sep 2004 23:57:06 -0700

Hi Allen and Nick,

I have run it myself on another desktop running Windows 98 and Office 2000,
so the problem exists on Office versions 2000 and 2003 and Windows versions
98, 2000 and XP Pro on both desktops and laptops. The machines are on
different LANS or even off the net all by their lonesome. One is running
Norton Anti-Virus with current definitions, one has Norton loaded, but the
definitions are over a year old. (It is not used on the internet) The other
computers are in other states and I am not sure what versions of everything
are running on them. I have a Windows 2000 machine I could try tomorrow as
well, but my friend told me he is seeing it there as well.

Here is the error on the 98 machine:

MSACCESS caused an invalid page fault in
module USER32.DLL at 017f:bff55472.
Registers:
EAX=0000001c CS=017f EIP=bff55472 EFLGS=00010202
EBX=00000000 SS=0187 ESP=0062efc8 EBP=0062efd0
ECX=00000918 DS=0187 ESI=0000001c FS=4b2f
EDX=00000000 ES=0187 EDI=000008fc GS=0000
Bytes at CS:EIP:
ad 3b c8 7c 10 ad 3b d0 7c 0b ad 3b c8 7d 06 ad
Stack dump:
00000000 0062f7a8 0062eff0 301576bb 0000001c 00000918 00000000 00000914
0062f974 0062f95c 0062f89c 3022451b 00000918 00000000 00000001 00000000

Originally the error was seen during QA on a new system being developed with
lots of data in the database. This is a migration from Excel to Access. In
order to isolate and reproduce it I wrote a small program that only has the
problem by itself.

There is no network printer, but I have a printer I can attach to any of the
machines.

Access was installed in different years from different CDs.

My laptop has current service patches and updates. The Windows 98 machine
does not.

I wish I could attach it here because the mdb file is only about 112K

Thanks,

Caryl Rahn

"Nick Coe (UK)" wrote:

> To add to Allen's questions -
>
> Are all these machines networked?
>
> Do they share a network printer? Do you have a default
> printer set in Windows?
>
> Are you using the same antivirus on all these machines? Is
> it on all the time?
>
> Did you install Office from the same cd or admin install set
> to all these machines?
>
> Are all these machines running a firewall (zone alarm or
> whatever)?
>
> --
> Nick Coe (UK)
> www.alphacos.co.uk
>
> ---
>
> "carylrahn" <carylrahn@discussions.microsoft.com> wrote in
> message
> news:5B4F49F4-01D3-48D3-8CB2-DB5596C663C0@microsoft.com...
> > Hi Allen,
> >
> > The probelm exists on 5 different computers. I know for
> sure that 3 of them
> > are totally differnet. I have a Dell 8600 laptop and two
> of them are
> > different types of desktops. I can make it happen remotely
> on one of the
> > computers as well using GoToMyPC.
> >
> > The error I get is:
> >
> > AppName: msaccess.exe AppVer: 11.0.6355.0
> AppStamp:40aa97a8
> > ModName: user32.dll ModVer: 5.1.2600.1255
> ModStamp:3f731c7d
> > fDebug: 0 Offset: 0000461d
> >
> > Does this help? In my recreation of the problem to isolate
> it, I have no
> > tables, just a form with 2 subforms and one report. None
> of them attempt to
> > access a recordset.
> >
> > I am so stuck!
> >
> > "Allen Browne" wrote:
> >
> > > Okay: you are narrowing this down.
> > >
> > > The report had no data, but still crashed.
> > > Can I assume that it had no RecordSource at all?
> > > If so, it is clearly not a JET problem, and is starting
> to sound like a
> > > Windows problem or bad video driver.
> > >
> > > To test if Windows XP is a factor:
> > > If you are using Windows XP, close Access, right-click
> on the desktop, and
> > > choose Properties. Set the Theme to "Windows Classic".
> Then test the report
> > > again.
> > >
> > > To test if the video driver is the problem:
> > > Right-click the desktop, and choose:
> > > Properties | Settings | Advanced | Troubleshoot
> > > Set Hardware acceleration to None.
> > >
> > > If you can't find the settings there, or are using a
> different version of
> > > Windows, go to the Control Panel, and try under Display
> Settings.
> > >
> > > It would be worth checking out if you can get an updated
> driver for your
> > > video card anyway.
> > >
> > > Hopefully that line of investigation will help track
> down the cause.
> > >
> > > --
> > > Allen Browne - Microsoft MVP. Perth, Western Australia.
> > > Tips for Access users - http://allenbrowne.com/tips.html
> > > Reply to group, rather than allenbrowne at mvps dot org.
> > >
> > > "carylrahn" <carylrahn@discussions.microsoft.com> wrote
> in message
> > >
> news:89C1867A-A85A-4ABC-BDBA-FD30934A12AD@microsoft.com...
> > > > Hi Allen,
> > > >
> > > > I appreciate the information, but I can recreate this
> and have with a
> > > > database with no data in it. I actually found out a
> little more today. If
> > > > I
> > > > open a report preview from a button on a form and then
> go to the scroll
> > > > bar
> > > > on the fom and click, Access will crash whether the
> report preview was
> > > > closed
> > > > or not. If I click anywhere else first the crash does
> not happen.
> > > >
> > > > The probelm happens on both Office 2003 and Office
> 2000. I have the
> > > > Professional Edition.
> > > >
> > > > Thanks, Caryl
> > > >
> > > > "Allen Browne" wrote:
> > > >
> > > >> This is probably some form of corruption.
> > > >> What version of Access? And which service pack?
> > > >>
> > > >> To rebuild it, try this sequence:
> > > >> 1. Uncheck the boxes under:
> > > >> Tools | Options | General | Name AutoCorrect
> > > >> Explanation of why:
> > > >>
> http://members.iinet.net.au/~allenbrowne/bug-03.html
> > > >>
> > > >> 2. Compact the database:
> > > >> Tools | Database Utilities | Compact.
> > > >>
> > > >> 3. Decompile a copy of the database by entering
> something like this at
> > > >> the
> > > >> command prompt while Access is not running. It is all
> one line, and
> > > >> include
> > > >> the quotes:
> > > >> "c:\Program Files\Microsoft
> office\office\msaccess.exe" /decompile
> > > >> "c:\MyPath\MyDatabase.mdb"
> > > >>
> > > >> 4. Compact again.
> > > >>
> > > >> That may be all you need to do. If it is still
> faulting at this point,
> > > >> the
> > > >> next step would be to follow the 5 steps for the
> first symptom in
> > > >> article:
> > > >> Recovering from Corruption
> > > >> at:
> > > >>
> http://members.iinet.net.au/~allenbrowne/ser-47.html
> > > >>
> > > >> "carylrahn" <carylrahn@discussions.microsoft.com>
> wrote in message
> > > >>
> news:70838EDB-6DA5-4F96-8DCB-ECED4B290F52@microsoft.com...
> > > >> >I have a form with a print button. It brings up a
> print preview. When I
> > > >> >close
> > > >> > the print preview the form is back on the screen.
> If I click the scroll
> > > >> > bar
> > > >> > it will crash Access every time. I can reproduce
> the error at will.
> > > >> > This
> > > >> > is a
> > > >> > show stopper for my application and I already
> posted a question about
> > > >> > this
> > > >> > a
> > > >> > few days ago. Can someone please help.
> > >
> > >
> > >
>
>
>

Quantcast