[EMAIL PROTECTED] wrote on 06/09/2006 11:40:36 AM: > Pointing out the obvious was very helpful, thanks. Gives me great > confidence in dealing with IBM on odd issues such as this. > > We're dealing with report code written by a vendor (who knows what bizarre > reason they had), and found the issue when the report wasn't returning > expected results. We know using external dates work. We know having a > dict item without the conversion works. We also know that using the > bizarre scenario of an internal date against an external field works. What > we don't know, and hence the question being posted, is why only this date > range of 14001 - 14365 does not work.
You are providing dates in external format. YYJJJ is a valid external format. Before you proclaim this as a bug in UniVerse, try it in other databases. I suspect that if you go to a legacy pick system and try this, you'll get the same results. This behavior is by design, and is in support of legacy systems. Try 10001, 18365, and other such ranges. I suspect you'll find that they behave similarly. Face it - you're supplying data that is not consistent with the intent of the dictionary item. Anything that doesn't resolve to an external date will just be passed through. Tim Snyder Consulting I/T Specialist , U2 Professional Services North American Lab Services DB2 Information Management, IBM Software Group 717-545-6403 [EMAIL PROTECTED] ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
