tag:blogger.com,1999:blog-5585680429157536914.post147107797184565312..comments2023-12-19T01:06:46.450+00:00Comments on QlikView Addict: When QlikView Data Types Go WrongMatt Fryerhttp://www.blogger.com/profile/16375702764551893303noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5585680429157536914.post-53242195627934872252013-11-15T15:39:29.444+00:002013-11-15T15:39:29.444+00:00Hi! I have a similar problem, I did that, and work...Hi! I have a similar problem, I did that, and working. But, Nowdays I need use Direct Select to access more info from my DB, and I can't format using Direct Select. Do u know something about that?Gustavohttps://www.blogger.com/profile/05135285852580109528noreply@blogger.comtag:blogger.com,1999:blog-5585680429157536914.post-6229009602730187932012-03-19T10:12:54.688+00:002012-03-19T10:12:54.688+00:00Hey, I've stumpled on often. I'd prefer to...Hey, I've stumpled on often. I'd prefer to use the database server to define this correctly. Qlikview honers a strongly defined database. <br /><br />A similar thing happens if you have a numeric key that is more than 16 chars in length, then it needs to be defined as text. Else it end up as 1.23456789012345*10^2 which messes up the key.<br /><br />/SeebachSeebachhttps://www.blogger.com/profile/03360932967834078965noreply@blogger.com