I solved mine using an extension function (being in a hurry). A native XSLT solution should of course be possible. But of course, it will all be guesswork until we get a sample input, desired output from this sample and a sample XSLT document that has the XSLT code that creates the memory error. Regards, Ragulf Pickaxe :-)
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[no subject], Unknown | Thread | |
[no subject], Unknown | Date | |
Month |