Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Odd error message "can't open a form whose query..."

Status
Not open for further replies.

jsteph

Technical User
Joined
Oct 24, 2002
Messages
2,562
Location
US
I get the below error in access97:

Can't open a form whose underlying query contains a user-defined function that attempts to set or get the form's recordsetclone property
When I run a query. The query contains one function Len()--not even a user defined one.

There are no forms whatsoever in this mdb--it's a scratch db I created and have just a couple of local jet tables and a couple of odbc-linked tables. Again--no forms, no reports, no user-defined functions. I'm just opening a query that looks at a jet table and gets the len() on one of the fields.

I googled the err msg and found nothing, I was just wondering if anyone has seen this?
--Jim
 
Sounds strange, have you tried repairing the database?

If that doesn't do anything I would create a new database and import the tables and queries into the new one.

Sounds like it may be corrupted.
 
I've never seen it, my bet is the ODBC table links are causing the weird behavior.
 
Thanks for the responses. There's one other possible explanation, but I checked and the timing doesn't add up. I'm working on a terminal server from home, and I have a few scheduled tasks that are Access db's that run and do a few things.

So I thought maybe it was from one of those tasks, yet none of the task run times were close to when this happened (and they only run a few minutes), plus, the times when I'm on the server and those tasks do run, I see them pop up and I have to minimize them to keep working. When I got this particular error, the db I was working on was the only thing open.

The db was near max size, in fact as I was moving data I had to compact it once when it got too close to max, but it never showed any corruption signs and worked fine but for that one error. It hasn't happened again so for now I'll chalk it up to 'one of those things'.
--Jim
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top