Deleting VB class objects that won't delete

RCC

New member
Local time
Today, 10:35
Joined
May 2, 2008
Messages
7
I'm fairly new to Access. I created a number of reports and then deleted them (Access 2000). If I go into VB editor they still appear and if I right click the remove command is shaded. If I click on the object name I get an error box stating "report name misspelled or doesn't exist".

Access 2000 will start the DB with no msgs. If I try to start this DB on Access 2003 or 2007 I get 4 msgs per object that I need to get rid of. After going through all the msgs the DB runs o.k.

Can anyone tell me how I can delete these objects?
 
Before you deleted originally, did you have or create a backup? :rolleyes:
 
backups

I have perhaps 10 backups but none prior to the problem, which did not show itself until I tried running the DB under 2003.
 
I created a number of reports and then deleted them (Access 2000).

And this was accomplished from the Database | Objects list?

If I go into VB editor they still appear

Still appear where? In the Projects list?

Did you try from the main menu from Access 2000: Tools | Database Utilities | Compact & Repair Database... ? Then try to open it from 03/07
 
deleting objects

In the VB editor,
under PROJECT - DB name
under MICROSOFT OFFICE ACCESS CLASS OBJECTS
Form_Form1
Form_frmNARRATIVE_XREF
Form_Switchboard
Report_1
Report_2
Report_3

This is what I see. If I select one of these, it tells me, "The report name 'Report_1' you entered in either the property sheet or macro is misspelled or refers to a report that doesn't exist."

I haven't run the DB through the compaction/repair function for awhile. I will give it a shot.
 
property sheet or macro

When you deleted the reports did you also delete all peripheral references and or macros associated with those reports as well?

Not trying to be a smart a** but, it is never a good idea to make User View, Business Rule and or Coding changes to your production db. Changes should be made to a copy and that copy should never be a stored back up.
 
Deleting objects that won't delete

I wasn't aware I created macros with a simple report. Automatic, I suppose?

Secondly, these DBs are all in a test status. I wasn't aware I had a problem until I attempted to run under 2003/2007.

Thirdly, what is a peripheral reference?

Fourthly, I tried compaction/repair. Now I only get the message for each object twice rather than four times.

Fifthly, do you suppose I could make a simple report, using a report name of one of my problem objects, then get rid of everything? If that would work, what would be the proper sequence for deleting?

Sixthly, thanks for your input thus far!
 
The error seems be telling (which is not always the case: error messages are oftentimes vague) you by the opening of the report, some outside macro or routine is being triggered. What is really strange is the fact they yet appear in the project list.

Is there a 'References' list in your VBE Projects list? It is possible I suppose there is a 'ghost' copy of a Access 2K version of your db that is being referenced and that copy yet retains those reports. But I would think you would also get a 'Missing References' error. Check Tools | References and see if you have a reference to a previous copy of an Access 2K copy of your db. - just a thought and before coffee too :eek:
 
Deleting objects

Thanks for your thoughts. The references contain no 'extra' DB references that I can see. There are five boxes checkmarked which I will chat with you about a little later. I have to make some changes to the DB before getting back to the problem at hand.
 
Just import everything into a new mdb file. That should get rid of any garbage hanging around.
 
Deleting VB class objects

Bob Larson,

Your suggestion was right on target. It worked! A great big thanks!

Reid
 
Bob;

Why is it the obvious and simple is what is the most ellusive? :rolleyes:
 
Deleting

Bob;

Why is it the obvious and simple is what is the most ellusive? :rolleyes:

If we would employ this 'simple' (sic) philosophy more often think how much time we could save.
 
GladWeCouldHelp.png
 

Users who are viewing this thread

Back
Top Bottom