I have a MS-WORD report that uses SUB_DOCUMENT.
The query that is used to do this SUB_DOCUMENT CALL, uses ORDER BY "number_field".
it happens that when the report is shown, it orders like this:
if there is a number bigger than 10:
1,11,12,13,14,2,3,4,5,6,7,8,9,10
if there is no number bigger than 10, it works ok.
it seems that the "number_field" its beeing consider a plain text number.
Anyone has a problem with that?
By the way... i'm using version 6.0
Order by problem in SUB_DOCUMENT
Re: Order by problem in SUB_DOCUMENT
Another update
The attribute is a number and I tried formatting "00" and the same thing happened
It orders like this
01,02,11,12,13,14,03,04,05,06,07,08,09,10
I don't understand why....
The attribute is a number and I tried formatting "00" and the same thing happened
It orders like this
01,02,11,12,13,14,03,04,05,06,07,08,09,10
I don't understand why....
Re: Order by problem in SUB_DOCUMENT
I created a new Query and a new PLAIN TEXT attibute to CONCATENATE the sequence number hoping it could be a number/string problem.
So using this attribute, the Query that is called on the SUB_DOCUMENT action, works perfectly
But when is processed on word, it gets all messes up AGAIN.
It's THE SAME query!!!
It works OK on the RUN QUERY, but it won't work on MSWORD.
Any suggestions? My clients are having to generate the report, open MS Word, REODER MANUALLY and save the document again... it's awful!
So using this attribute, the Query that is called on the SUB_DOCUMENT action, works perfectly
But when is processed on word, it gets all messes up AGAIN.
It's THE SAME query!!!
It works OK on the RUN QUERY, but it won't work on MSWORD.
Any suggestions? My clients are having to generate the report, open MS Word, REODER MANUALLY and save the document again... it's awful!