>Shouldn't it be?
>

>cmdstr=[alter table ]+lctable+[ alter column ]+lcfld+[ DROP DEFAULT ]
>

>

Unfortunately I get the error either way. If I MODI the table and manually erase the two defaults that are based on an objref I can then remove the others which call functions with either DROP DEFAULT or just DEFAULT with no expression passed. But if any field has an objref default the alter table will fail on any field.

Strange.

I thought I might be able to hack the DBC but it seems default values are in the same mystery memo with other field attributes and I'm not sure I could programmaticaly STRTRAN is out of there without breaking something.



>>I inherited a DBC full of tables that have default values set at the table level. Generally this is something I don't do since I use views exclusively to insert records, but normally within my framework the values being there is no problem.
>>
>>But some of the DEFAULT values are object references like
>>
>>This.oapplication.osecurity.cuserid
>>
>>Make sense in the context of a VFE app but not a good thing for my conversion program as I massage and upsize the data for SQL Server.
>>
>>Okay, so I want to get rid of the default values for all fields in all the tables.
>>
>>In a prg I cycle through the tables and fields, and for each field I do
>>
>>cmdstr=[alter table ]+lctable+[ alter column ]+lcfld+[ DEFAULT ]
>>&cmdstr
>>
>>If the table contains any default values with This. I get an error the first time I try to run this ( even if that field isn't the one that has the objref default value ) saying I can only use "This" inside a method. Of course I am not trying to use it, just drop it. Seems alter table should be smart enough to know that ...
>>
>>Am I using the ALTER TABLE syntax wrong to clean out a default value?
>>
>>I could a class, I guess, and run this stuff as a method etc so obj ref would make sense but seems like there should be a way to do this without that.
>>
>>Thoughts?
>>
>>TIA