[AccessD] RE: Access 2002 - Another Annoyance

dmcafee at pacbell.net dmcafee at pacbell.net
Fri May 27 11:22:35 CDT 2005


I hate it when Access tries to be "too smart" for its own good. I'm sure the
MS programmers were trying to validate something (with good intentions). I
hate it when they do that, just like when trying to import an Excel file
with numbers in a column, but you really want to import that column as text.
Access wont let you :|

David

-----Original Message-----
From: Heenan, Lambert

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




More information about the AccessD mailing list