You were right, nagornyi, The problem was un-reproducable. I found it was caused by a CHR(13) being placed at the start of the string in some situations. Removing this fixed the problem. I should have noticed this earlier.
Thanks for taking the time though...
I tried the sugestion above and found that the result was the same - although it was worth a go. The outcme of this was that I had to test the length of the string in th estored proc and insert a char(10) maually using the mod() function, which became a little ugly but it worked.
Thanks for...
Hi
Thanks for your suggestions. It probably won't be until next week before I get a chance to look at this again, in which case I'll look at putting together a sample.
Cheers
Hi all
I have a field (A) with 'vertical elasticity' set to 'expand' because it can contain many lines. The neighbouring field (B) has the same setting. When field B has more lines than field A the contents of field A are aligned vertically to the bottom causing white-space at the top. is...
Hi all
My client has requested that a 'non-breaking space' be placed between 2 words so that they always appear on the same line (eg '[13 offences]'). Is there a way to do this?
I've read that ascii char 160 is supposed to be a non-breaking space but this doesn't appear to work (by inserting...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.