Weird issue

  • Thread starter Thread starter Tara
  • Start date Start date
T

Tara

I'm not even sure where to post this, but I guess this is as good a place as
any...

I was woking on a database and attempted to open an update query in design
view. As soon as I right-clicked on the query and clicked design view, the
whole databased closed! I've tested it with other queries and it's fine.
It's only with the one query. What in the world is going on???

Any help is appreciated!
 
I'm not even sure where to post this, but I guess this is as good a place as
any...

I was woking on a database and attempted to open an update query in design
view. As soon as I right-clicked on the query and clicked design view, the
whole databased closed! I've tested it with other queries and it's fine.
It's only with the one query. What in the world is going on???

Any help is appreciated!
Click to expand...

What Access version? What service packs? Have you tried Compact and Repair?

And... very crucial here!!... do you have a working backup?
 
The query is corrupt and therefore maybe the entire database file. Your best
bet is to create a new database and import everything EXCEPT for the problem
query. Then rebuild the query.

For more corruption information:

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp
 
Access 2000. I've tried compact and repair. Yes, I do have a backup, but I
just did A LOT of work to this one today and I hate the idea of having to
rebuild it all. Guess I'll have to though.

Thanks.
 
Thankfully, I have a backup that's working, but I did a lot of work to this
copy today. I hate to redo it all, so hopefully your suggesstion of
importing everything (except the query of course) into a new database will
work.

BTW ~ I've never really understood how corruptions happen. Can you give me
a quick overview?

Thanks,

Tara
 
The resources listed explain in some detail, but for the most part, it's just
one of the mysteries of the universe.

Things like a power outage shutting down a computer might cause it. WiFi and
Access don't play well together. If the database is out on a network,
something like a bad network card (NIC) can cause problems. Doesn't even have
to be a NIC using the database; just something spewing bad packets. Memo
fields prone to corruption problems so I avoid them if possible.

Another problem is that Access is basically "all your eggs in one basket" as
everything is in one file. One of the best things to prevent, or at least
minimize, corruption problems is to split your database between a Front End
with all the forms, reports, queries, modules, and macros; and a Back End
with just the tables. Compact and repair can fix many table problems but
doesn't do so well on the rest. Also a bad form or report might just lock up
the entire file making it unusable. Therefore data in the BE is safter
without all the other database objects.
 
Tara,

When you use the Import dialog to import all the old objects into the new
database file, be sure to not click on the Select All option in the queries
tab. I just recently learned that it is better to select all of the good
queries individually, rather than using the select all and unselecting the
bad one.

Cannot remember the explaination, but when I did it (select all, then
unselect) the new database was still corrupt, but when I did it by selecting
each query separately, it worked fine.

--
HTH
Dale

Don''t forget to rate the post if it was helpful!

email address is invalid
Please reply to newsgroup only.
 
Jerry Whittle said:
The resources listed explain in some detail, but for the most part, it's just
one of the mysteries of the universe.

Things like a power outage shutting down a computer might cause it. WiFi and
Access don't play well together. If the database is out on a network,
something like a bad network card (NIC) can cause problems. Doesn't even have
to be a NIC using the database; just something spewing bad packets. Memo
fields prone to corruption problems so I avoid them if possible.

Another problem is that Access is basically "all your eggs in one basket" as
everything is in one file. One of the best things to prevent, or at least
minimize, corruption problems is to split your database between a Front End
with all the forms, reports, queries, modules, and macros; and a Back End
with just the tables. Compact and repair can fix many table problems but
doesn't do so well on the rest. Also a bad form or report might just lock up
the entire file making it unusable. Therefore data in the BE is safter
without all the other database objects.
Click to expand...
 
Jerry, On a personal note. Are you from AL and were you stationed at
Lakehurst? If you are the right one, please reply (e-mail address removed).
 
I'm not even sure where to post this, but I guess this is as good a place as
any...

I was woking on a database and attempted to open an update query in design
view.  As soon as I right-clicked on the query and clicked design view, the
whole databased closed!  I've tested it with other queries and it's fine..  
It's only with the one query.  What in the world is going on???

Any help is appreciated!
Click to expand...

Hi,

Sounds like the database is corrupt or something. If necessary, I
think you can try a utility called Advanced Access Repair to repair
your Access MDB file. It works rather well for my corrupt Access MDB
files. Its web address is http://www.datanumen.com/aar/

Alan
 
Back
Top