deleting Access artifacts

[mitchmcc]

I inherited an Access application that I have made some changes to.
When I start it up, I am getting several errors that appear to be referring
to old tables or queries. Nothing that is currently really part of the app
is wrong.

Here is the message:

The record source '~sq_cEmployee Certification Tracking ~sqclstAlerts' specified on this form does not exist.

I found something online that showed how to get Access to dump every
SQL object, and in that output, I see what I think are a bunch of garbage
queries that do NOT show up in the Object browser.

Here is an example of what I mean:

SQL name (4): ~sq_cEmployee Certification Tracking~sq_clstAlerts-----------------------------------------------
SELECT CertificationAlertsRaw.Alert AS Expr1
FROM CertificationAlertsRaw
WHERE (((CertificationAlertsRaw.Alert)="Yes"));

Note the weird name with the tilde.

It almost looks like these are artifacts from a crash or else perhaps
an Access bug?

There are about 30+ of these.

If these things are, as I suspect, what is causing these error messages


at startup, how can I get rid of them, since they don't show up in the
Object browser window?

Thanks,

Mitch

[June7]

Have you run Compact & Repair?

Right click on the Navigation pane header > Navigation Options > check: ShowHiddenObjects and ShowSystemObjects. This will reveal some tables. The MSysObjects might show some entries that have Name with the tilde character. I don't know what happens if you delete a record here. Related records are in MSysQueries. I didn't look for related records in the other Sys tables.

If C&R doesn't work, best bet might be to import working objects and code to a new project.

[mitchmcc]

It does appear that these objects are in the MSysObjects table, e.g.

~sq_cEmployee Certification Tracking Old~sq_ccboCertifications
~sq_cEmployee Certification Tracking~sq_clstEmpl

etc.

I did do a "Compact and Repair", but it did not delete these objects, and
neither did it fix the problem. I am still getting errors that reference these
old tables/queries with the old schema! As I noted before, all of the regular
tables, queries and reports that are currently being used do NOT reference any of these old items that are giving the errors... only these ~ items.

Do you (or anyone) know what these MSysObjects items represent, and if
it is actually safe to delete them?

Mitch

[June7]

You can try and see what happens. Make a copy you can roll back to if really blows up.