[AccessD] Access 2002 - Another Annoyance

Too thorough and yet too stupid at the same time! 


John B.


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert
Sent: Friday, May 27, 2005 9:31 AM
To: 'ACCESS-L Email (ACCESS-L at PEACH.EASE.LSOFT.COM)'; 'Access-D Email
(accessd at databaseadvisors.com)'
Subject: [AccessD] Access 2002 - Another Annoyance

X-posted to Access-L and Access-D

Here's another little gotcha about Access 2002 that you might want to know
about.  

I'm sure many  people are aware that when you suspect that the mdb has
become corrupted that a way out of the problem is to create a new blank
database and then import all of the objects in the problem database into the
new one. That often fixes the issue, and leaves you with a nice 'clean' mdb
to play with.

Well I just tried to do that and hit a problem. I have some saved queries in
the mdb which reference a temporary table that only exists after some code
is executed. During the import process Access complained that it could not
find the table and the only buttons I had were 'Ok' and 'Help', so I just
wound up in an infinite loop of complaints about the missing table. The end
result being that it was impossible for me to import all my objects, unless
I excluded those specific queries.  Fun and games! :-(

Lambert
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com