asked on

Mystery Table

Hello~
I have a macro that deletes everything in a database and imports it all from another one. Basically it is a test database that I refresh from the production database.

Since I have upgraded from 2003 to 2010 I have some mystery table that does not exist that the macro is trying to delete and recreate:

f_8D747EB0995F4AC8A581B559AAA87112_data

I'm extremely confused. Has anyone ever seen this or know what it is? It doesn't exist in the database anywhere so my macro on delete gets stuck on it and I have to drag past it and my macro on import I have to drag past it in the code.

Appreciate any thoughts.

Thanks!
Deanna

mbizup

Possibly something that was automatically created in the upgrade process.

Try, from the navigation pane ..

- Right-click the header bar on the navigation pane
- Click Navigation Options
- Check the boxes to show System Objects and Hidden Objects

... and check the contents of the table if it appears at that point.

dminx13

ASKER

Nope. Isn't there :-( we have tons of hidden things so that was already checked.

ASKER CERTIFIED SOLUTION

jadedata

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

mbizup

Wow! A blast from the past. Nice to see you around these parts, jadedata!

Helen Feddema

If Compact & Repair doesn't eliminate the mystery table, make a new database and import all legitimate objects from the problem database into it; that should leave the problem table behind.

DatabaseMX (Joe Anderson - Former Microsoft Access MVP)

"MSAccess is still young and gets confused easily."

?

dminx13

ASKER

I'll give the making a new database and see if that works. The Compact & Repair did not.

dminx13

ASKER

Tried the new database no go. Still said it existed. So then I dug further and it is referenceing the MsysObjects table to get things from. So why does the MSysObjects Table have this weird file? How do I get rid of it there? What is really odd is that it doesn't try to do everything in this table at all. So why pick this one up?

SOLUTION

dminx13

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

dminx13

ASKER

I ran with what Jade said about the separate table and found that I was already looking at one so I just needed to update the code to ignore the new weird table!

jadedata

nice job on that ..

hey mbizup! good to be back for a bit.

dminx13: Access is a standalone operation,.. all objects in one container called an mdb or accdb.. as such, and in order to hide control objects from users (a long time microsoft tradition..) you will frequently find "weird" tables and things you didn't create in your mdbs.

If you use naming firm conventions on your objects, even those specific to the project and stick with that pattern as you build new projects you can navigate through your project and know at a glance what's yours and what is MSAccess junk objects

Once it's a habit these utility chores of leger de main will be a cake walk

dminx13

ASKER

Yes, we have standard nameing conventions so it was easy to identify the tables that come with access and that magically showed up! Even if your can't see it. Very odd. Not a hidden object. Access just thinks it exists!

Eventually we hope to convert to SQL. It would have been nice to do that now, but we were under tight time constraints to upgrade to Office 2010 so we just did this as an interim solution.

jadedata

best of luck on the conversion

may all your projects be easy and your code be bug free!