On 14 Jan 2004 14:54:01 -0800,
pbbriggs@yahoo.com (pbbriggs) wrote:
Does the recordsource of your form (or subforms) include a join to a table used to lookup related data for display only on your form?
I have had 3 "shutdown" problems with A2K2 which were all caused by the use of a join to a lookup table. All were fixed by removing the lookup table
and replacing it with a direct DLookup / TLookup to the table from the display control on the form.
Further info in -
http://www.google.com/groups?hl=en&l...4ax.com&rnum=3
[color=blue]
>I will try to be as descriptive as possible, but this error has me
>stumped and I am not sure what relevant info to include....
>
>I am running Access XP on a Windows XP machine. I initially began
>developing an app in Access 2000 but converted it several months ago
>to XP. So the app is now Access XP format also.
>
>My app is crashing on a regular basis, with the totally non-descript
>Microsoft error (Microsoft Access has encountered a problem and needs
>to close. Do you want to send an error report to Microsoft?). Every
>time, I send the error report to MS in the vain hope that this might
>accomplish something. One time I actually received a response from
>them, telling me that they were aware of a bug in Access XP that might
>be causing my error, and that the bug would be fixed in Office XP
>Service Pack 3 (which still has not been released).
>
>Anyway, I'm not entirely convinced that it's a MS error because it
>does not happen with regularity on the same event(s). The error
>nearly always occurs on one particular form, when I click a button
>that performs a series of queries based upon some "If Then"
>conditions. After performing the queries, the main form (on which the
>button is located) also performs a requery of two subforms (which are
>continuous forms). All of this works fine (the queries, the If
>conditions, and the two Requery events), so I do not believe I have a
>code issue. However, about one time in every 10 (or 20, or so), I
>click the button, the queries will run, and then (I think as it is
>attempting the requery), I get the error and Access shuts down. What
>I have noticed is that if I temporarily move the back-end off our
>server and onto a local PC (where the front-end is housed), the error
>occurs much less frequently (maybe once in every 50 tries instead of
>once in every 10), which makes me think it may have something to do
>with the timing of performing the queries and then attempting the
>"requery" before the queries are finished. Otherwise, though, the
>FE-BE setup seems to work fine (no real speed issues or anything).
>Also, I am the only one using the app right now, so it's not an issue
>of multiple users trying to access it at the same time or anything
>like that.
>
>Anyhow, I know there may be no one that can help based upon this
>amount of information, but I am certainly open to any suggestions.
>
>Based upon some others' helpful suggestions, I have tried the
>following steps without success (i.e., I still get the same crash
>every 10-20 attempts or so):
>
>1. Creating a new .mdb and importing all of the objects
>2. Inserting DoEvents before the Requery (as well as after each
>individual query)
>3. Changing all query calls from Docmd.OpenQuery to CurrentDb.Execute
>4. Inserting DBEngine.Idle dbRefreshCache before the Requery
>5. Un-binding the forms, running the queries, then re-binding the
>forms before the Requery
>
>None of these actions seems to have any effect that I can tell. It
>would be easier to debug if it crashed every time, but it doesn't.
>
>Thanks in advance for any help.[/color]
Wayne Gillespie
Gosford NSW Australia
