From what I've read, the
dtproperties system table contains information regarding diagrams stored in a SQL database. However, it seems there is some other logic to how and when it gets created.
Here's the scenario:
I'm creating a new database that has no diagrams internally. All of the tables were created via script at essentially the same time (a couple hours ago).
At the moment, I am working on a script to create some stored procs programmatically for all of the user-defined tables. The script gets a list of these via the following query:
select SO.Name from sysobjects SO
where so.xtype = 'U'
According to Enterprise Mangler,
dtproperties is a system table. So, this query should ignore it. However, my script coughs up a furball because
dtproperties is included. A quick query of sysobjects where name = 'dtproperties' shows, in fact, that xtype = 'U' (but I would have expected it to be 'S' for a system table).
Getting back to Enterprise Mangler,
dtproperties shows a creation date of just a few minutes ago, even though there are no diagrams in the database. Huh?
Anyone know what is going on? I'm curious as to (1) why the table would be created automagically, when there are no diagrams, and (2) why it is listed in sysobjects as a user table.
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.