Maybe it's just a "bug" in the application - I.e. should be doing OCONV() in Select. Have you checked with your Vendor?
Mark -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, June 09, 2006 8:41 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] UniVerse Internal Date Blackout 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. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
