one parameter crashes app

  • Thread starter Thread starter IMK
  • Start date Start date
I

IMK

In an app I made with Access 2k there is one query that I created as part
of a dynamic report interface that causes the whole app to crash. I get the
basic memory error (error number 0x1b0564df, if it matters). I looked on the
Microsoft site for articles on that particular error but came up with
nothing.

The query is this:
SELECT qryPostQAReview.SubName
FROM qryPostQAReview
WHERE qryPostQAReview.SubName = 'Methadone';

When I recreated this query in the SQL editor and ran it, it only flashed,
it didn't give me an error message, just nothing. When I removed the WHERE
clause it ran fine.

I've got four other parameters for the users to choose from on this report
form. They all work, it's just this one parameter that kills the whole thing
(dramatically). They want to be able to use this parameter both by itself
and along with other parameters and I am stumped.

Has anyone dealt with anything like this?
 
hmmm
i don't see anything wrong with what you posted. If
there's an error it probably is elsewhere.

i would try repairing the database, and also running the
app on a different computer.

is there any code being executed? if so, try stepping
through the program and see exactly which line causes the
program to crash. the only time iv'e had a consistent
crash using access is when you do something that triggers
an infinite loop, like calling Requery from a listbox's
callback function
 
I still don't know quite what it was, but I did manage to fix it (for the
time being anyway). The problem seems to be linked to my having based a
query on a query. I do this quite often in code since changes to the one
query will cascade through all the places I use it, but in this case the
underlying query may have been too complex. All I know is that when I put
the actual original SQL statement into the code (as a string), added the
parameters and opened the recordset, it worked again.

Maybe I was pushing the envelope a bit.
 
Back
Top