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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem running a query on a particular machine

Status
Not open for further replies.

jocasio

IS-IT--Management
Oct 11, 2002
88
US
All:

I have a very strange problem that I cannot figure out. I have a query that I am creating and when I try to save the query, Access closes. I had a coworker load the query into his machine and it saves without a problem. he sent me the query and when I imported the query back into my DB, I could run it, but if I try to view it via design view it shuts down access. I'm at a complete loss as to why this is happening on my machine. The db is only 54 mb. I have access 2002 (xp).

Has any one ever come accross this? It seems as though a table name is making this happen, but again, it works on my coworker's PC.

Any thoughts would be greatly appreciated

jocasio
 
Does Access close without a message, or with one?

This strikes me as a corrupted file. I would try creating a new database, importing everything except the problem query, and then recreating the query from scratch.

If the problem persists after that, consider whether your database file is too deeply nested in folders. Although I thought it was fixed by Access 2002, earlier versions had a buffer overrun problem with paths longer than 128 (I think) characters. All kinds of bizarre things would happen, but they'd go away if you moved the .mdb file to a folder higher in the path.

Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein
 
Rick:

Thanks so much for your response. It is very bizarre behavior. I've exported all of my queries and several table to a new DB, and tried it and again, the same problem. I then sent the DB to a co-worker and it ran on his machine with no problem. He is in a different office. I put it on another machine here locally and it exhibited the same problem. I was creating a make table, so to get around this I first saved the query as a select query. Opened it back up and saved it as a make-table query. Trying to save it as a make-query origianlly would close the app.

Thanks for your help. If you or anyone have any other thoughts, please let me know.


jocasio
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top