Michael R Mattys
michael.mattys at adelphia.net
Sat Nov 1 22:12:08 CST 2003
Running the documenter creates a table in an access MDT file stored in your profile folder: C:\Documents and Settings\YourName\Application Data\ Microsoft\Access\ACWZUSR.MDT If you were to import doc_tblObjects and save it, you might be able to do some comparision with it. Maybe ... Michael R. Mattys Try MattysMapLib for MapPoint at www.mattysconsulting.com ----- Original Message ----- From: "John Colby" <jcolby at colbyconsulting.com> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Saturday, November 01, 2003 10:28 PM Subject: RE: [AccessD] ID in MSysObjects > No, Iknow about that. I was hoping for a persistant ID that I could use to > track database objects. > > > John W. Colby > www.colbyconsulting.com > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Michael R > Mattys > Sent: Saturday, November 01, 2003 10:15 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] ID in MSysObjects > > > John, > > It seems like you might be missing MSysObjects.Type? > ---- > The List of Forms - > SELECT MSysObjects.Id, MSysObjects.Name _ > FROM MSysObjects WHERE (((MSysObjects.Type)=-32768)); > > The List of reports - > SELECT MSysObjects.Id, MSysObjects.Name _ > FROM MSysObjects WHERE (((MSysObjects.Type)=-32764)); > > The List of Macros - > SELECT MSysObjects.Id, MSysObjects.Name _ > FROM MSysObjects WHERE (((MSysObjects.Type)=-32766)); > > The List of Modules - > SELECT MSysObjects.Id, MSysObjects.Name _ > FROM MSysObjects WHERE (((MSysObjects.Type)=-32761)); > > etc, etc, ... > ---- > > > Michael R. Mattys > Try MattysMapLib for MapPoint at > www.mattysconsulting.com > > > > ----- Original Message ----- > From: "John Colby" <jcolby at colbyconsulting.com> > To: "AccessD" <AccessD at databaseadvisors.com> > Sent: Saturday, November 01, 2003 9:50 PM > Subject: [AccessD] ID in MSysObjects > > > > Does anyone have experience using the ID field in MSysObjects? > > > > I assumed (bad, I know) that it was a PK and not reused. I built a table > of > > form attributes, and pulled the ID from MSysObjects table by joining my > > table name with the table name in MSysObjects, storing this ID in my table > > so I would have a reference back to the object in Access' MSysObjects. > > After a couple of weeks playing around (and ASSUMING my numbers were still > > good) I started trying to use this ID. I joined the ID in msysObjects > with > > the same FK in my table, and compared the name in my table with the name > in > > MSysObjects. In many cases they matched, in others they aren't even the > > same TYPE of object anymore. The ID now belongs to a module instead of a > > form. > > > > WTFO? > > > > John W. Colby > > www.colbyconsulting.com > > > > > > _______________________________________________ > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com