System Tables/Old References

S

Sprinks

I recently was asked to revive an old application that has sat for 3 years.
It had several tables that are now used by several other applications, and
reside in a general backend file.

Unfortunately, the common tables did not match exactly in structure or name,
so I was forced into the inelegant task of changing the backend tables'
structures, merging the data, and then rooting out all the references to the
old tables and fields in queries, forms, reports and code.

This was pretty gruesome, but the application appears to be working
correctly now with the linked tables from the common backend file, however, a
number of references to obsolete tables are in the MsysQueries system table,
e.g.:

Attribute Expression Flag LvExtra Name1 Name2 ObjectId Order
0 0 -2147483600
5 tblBuildingTypeList
-2147483600
6 tblBuildingTypeList.BuildingTypeID 0 -2147483600
6 tblBuildingTypeList.BuildingType 0 -2147483600
11 [BuildingType] -2147483600
255 -2147483600

tblBuildingTypeList is now called BuildingTypes.

My instinct is if it ain't broke, don't fix it, but was curious why these
references are there, and whether it is safe to delete them. Each seems to
come in a group bookended by attributes of 0 and 255.

Can someone help me understand this?

Thank you.
Sprinks
 
G

George Nicholson

The references are still there after a Compact & Repair?

Personally, I'm a little loathe to putz with the system tables. I would
consider creating a new, empty mdb file and import all objects into it
*except system tables*. System tables should get rebuilt automatically
during the import and if those references are no longer necessary, they
won't get created.

HTH,
 
Top