Mike hmm .. if i had been having a problem this might work. But i find it best to have the dictionaries actually define the data. So if/when we find something like this we simply run a routine against the data which lets us note and redefine as necessary.
DSig Tuesday, November 22, 2005, 8:17:44 PM, you wrote: HMM> David, >> -----Original Message----- >> From: [EMAIL PROTECTED] On Behalf Of David Tod HMM> Sigafoos >> Sent: Wednesday, 23 November 2005 16:06 >> To: Daniel Perttula >> Subject: Re: [U2] sql server & universe >> >> Daniel, >> >> SQL is pretty insistent on data being what it is defined as >> (a feature for some .. a drawback for others) >> >> Your best bet is to make your dictionaries match the data. >> Not sure I would actually make the fields lenght 999 but >> instead write a routine to examine the data and let you know >> the best size to make it. HMM> Doesn't HS.SCRUB do this for you? Then you can describe the data HMM> correctly in Attribute 10. HMM> Or HMM> Leave that attribute blank [except for fields which need correct HMM> description like DATE, or DECIMAL 12,2] and describe everything else on HMM> the SQL side as VARCHAR(255) HMM> HTH HMM> Mike >> If 13 char is the longest(in this case) then smudge to 14 if you >> think the data will change to that. >> >> Tuesday, November 22, 2005, 3:40:56 PM, you wrote: >> >> DP> Hello all - quick question for the SQL gurus out there, we have a >> DP> customer using SQL Server 2000 making queries to a UV 10.1.11 >> DP> server. We've noted that SQL Server errors out if the data in any >> DP> field matches or exceeds the field length specified in the field >> DP> dictionary. For example if we have a >> DP> dictionary: >> >> DP> WIDGET.PRICE >> DP> <1> A >> DP> <2> 100 >> DP> <3> WIDGET PRICE >> DP> <4> >> DP> <5> >> DP> <6> >> DP> <7> MD2 >> DP> <8> >> DP> <9> R >> DP> <10> 12 ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
