Question Why are my tables/queries invisible?

[DWayne]

I have been working on a personal finance database, and suddenly, I notice that both my tables and queries are invisible. All of them.

I know they are still there because the forms that use both tables and queries are working and generating all of the data. I also know that they exist somewhere locally because my database is stored on a flash drive and everything works regardless of which computer I use.

I need to add some extra tables to the database as well as alter the structure of the tables, but for the life of me, I cannot figure out where everything went, or at the very least why it's invisible.

I'm not completely daft with code, so if VBA is something that could bring back the visibility of all tables, I'd prefer to go that way.

Some other diagnostic flubs that seem to be related (they all started happening at the same time):

I cannot create macros. Whenever I try to save a new one, it suddenly says "Record is deleted". The macro remains in name, but there are no commands that I can add to it, and in addition, when I double-click the macro in order to have it run (and invariably generate an error and halt, because no form is loaded -- I'm okay with that), it does not reach that point and says something like it cannot find the macro.

Thanks for your help.

Daniel

 

[Kafrin]

I don't know about the Macro problem, might be worth trying a compact and repair.

As for your other problem, have you set any of the items to be hidden? If so then check your Options to see if Hidden Objects are visible.

If you have Modules that are invisible, then go into the VB code, go to View > Project Explorer, and you should be able to find your modules.

An alternative when anything really weird happens is to try importing your objects into a brand new database; if you can import them then at least you'd be able to see if they're still there, but if they're hidden then you'll still need to change your options to see them.

 

[DWayne]

Thanks a lot for the suggestion.

I've had several problems with this, programming it sometimes on my comptuer at home (Access 2007) and sometimes on the one at work (2002), so it's done a whole lot of "...has encountered an error and needs to close...", so I have a lot of backups, thankfully one from just last Friday. I ended up exporting all the new changes I had made to forms and such onto the backup file, then just renaming it to the original file. I only ended up losing a few records, but that just meant that I had to take the records from the original form (since I could still access forms) and rewrite them onto the backed up form (now labeled as the original).

Thanks for the suggestion, though. I don't doubt this will happen again, so you might be onto something.

 

[DCrake]

Is seems there may be a bit of corss contamination going on between your versions try to stick to one version whilst developing this cuts out any possibility of version conflicts.

David

 

[Kafrin]

Glad I could help

As David says, switching between versions for development is not always a good idea. I don't know about Access, but Word and Excel 2007 don't play too nicely with the earlier versions.

 

[DWayne]

Thanks, I think I'll just have to bring my laptop to work in order to work on it. Not too excited about that, but there seems to be no other way around it. Thanks for the suggestions, everyone.