*Access Closes in Response to Record Navigation*

[Dor100]

I've been experiencing total Access shutdowns in response to routine record navigation with a form. They nearly always occur in response to: clicking the first-record navigation arrow in the lower left area of form view; clicking the first-record navigation button created on the form using the Toolbox Command Button item; and using a normal look-up combo box to navigate to either the first or second record of the main form, but almost always not when using it to navigate to other records.

This problem is completely anomalous and unexplained.

Has anyone else seen this before? Application VBA has already been searched with nothing found that could cause this. Is there any way to determine the cause(s)? Is there anyway this can be caused by human intervention, external code, or modifying Access itself?

I've also tried reinstalling Office from the network (XP Pro) to no avail. If anyone has an answer, it would be much appreciated. Thanks.

 

[MajP]

Is this a new problems, that was not occuring before? Have you compacted and repaired the database? Can you post the code behind the navigation button? If I understand correctly you used the wizard to make this button. If that is the case, the code is often somewhat dated and uses things like "domenuitem" which is not recommended anymore.

 

[TheAceMan1]

How are ya Dor100 . . .

Because [blue]no error message is generated[/blue], corruption is crtainly indicated! I'd [blue]remove & reinstall[/blue] Office/Access. Then install [blue]the latest service paks![/blue] . . . [purple](no questions asked!)[/purple] . . . [blue]Its my experience this is eventually what you'll do! . . .[/blue]

See Ya! . . . . . .

 

[Dor100]

Thank you both for these posts. I did reinstall Office from our network, but unfortunately have no access to Office CD's and no control over what is kept on the network to draw from. When I check "About..." it says (Access 2002) SP3.

Interestingly, whenever I use the wizard to create a look up combo box, Access no longer adds the After Update code. This has been going on for a long time now, perhaps several years, although before, starting with Access 97, the code would originally appear as expected. I simply have to add the necessary code myself.

I tried repair and compact, copying the problem form, and just now creating a new form from scratch and copying the controls from the original form into it. The problems continue.

Here is the code behind the look up combo box (two event procedures):

Private Sub LookUp_Enter()

Me.LookUp.Requery
Me.LookUp.ForeColor = 0

End Sub

--------------------------------------

Private Sub LookUp_AfterUpdate()

Me.RecordsetClone.findfirst "Clients.ID='" & Me.LookUp & "'"
Me.Bookmark = Me.RecordsetClone.Bookmark
Me.LookUp.ForeColor = "16777215"
Me.ID.SetFocus

End Sub

The form's Current event merely sets LookUp's forecolor to "16777215" and the backcolor of a certain yes/no box's label depending on whether its value is true or false.

I haven't seen problems similar to this for a long time, to my knowledge not since around the time of the trouble that occasioned this thread: thread3-182589.

 

[Dor100]

Just did a Detect and Repair to no avail; am now checking for updates at Microsoft.com.

 

[Dor100]

I updated Office but the problem remains. Anyone have any more thoughts on this, or has anyone ever encountered or heard of this before? I'm particularly interested in finding out if this can be brought about intentionally by someone with access to the Office software kept on the network. Can a person hack or use third party software to set Access to behave in this manner? Does anyone know why the combo box wizard would no longer add the After Update code? We did have a problem in the past when the section in charge of providing the software had stripped it of normal wizards. Could they have partially disabled the wizard so the code does not get provided?

 

[PHV]

Does the DB compiles properly ?
menu Debug -> Compile ...

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[Dor100]

Yes, I've done that a number of times and just now, too. Is there any malware or other such garbage on the market that could bring this about, or can malicious code be made such that "if user x navigates to records y or z, or uses first record navigation buttons, quit app"?

 

[PHV]

Have a look here:

http://www.mvps.org/access/bugs/bugs0008.htm

http://www.granite.ab.ca/access/decompile.htm

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[Dor100]

The decompile went smoothly; I compacted two more times, but the problem remains.

 

[Dor100]

Just found and used the Microsoft tool at

http://www.microsoft.com/security/malwareremove/default.mspx

to do a full system scan: no malicious software found (only of the list it tests for, of course).

Plan to use these pages, although I may have already done most of what's on them:

http://www.pcreview.co.uk/forums/thread-2270100.php

http://allenbrowne.com/ser-47.html

 

[Andre25624]

Dor100:

I am experiencing a very similar problem, and I have noticed that in the two databases I am using that exhibits these problems, they have two things in common. One is that they are navigated using a bookmark, and two that they contain an picture control. what I have noticed interesting is that using the wheel mouse or pageup/pagedown buttons, the problem does not exsist!

To sort this out for me, can you tell me if you have picture object controls, and if the use of other navigation methods cause the same outcome?

Andre

 

[AMG410]

Dor100:
I had the same problem today and after trying all the previous suggestions. I tried the following and it worked. When I would use the record navigation buttons, the custom buttons on my form would no longer work and I could not close the form. I could however keep using the navigation buttons.
My Solution (hope this helps)
1. I copied the code from the form causing problems.
2. In the form properties, selected "No" for "Has Module", which deleted the code module for the form.
3. Created a new code module by setting up the event for one of the buttons.
4. Pasted the copied code into the new VB module.