I just spend some time to recreate user interface behaviour from our previous Navision system. Somebody else might like to use this too but if not, at least I know where to find it if it crosses my path again.[:)] When entering comment lines the standard behaviour is to beep at the end of the line. In our old system users could just keep entering. At the end of the line the input is switched to the next line automatically. To create this behaviour you need to go to the properties of the field in the form. There you set the property AutoEnter to Yes AND the property NextControl to its own ID.
hmm this used to be standard, they must have changed it
Digital Vantage Point has a nifty solution for entering comments. You have a RTF editor with wordwrap so you type of your comments (without beeps [:)]) and when you’re done the add-on will cut up the text you typed so it fits into Navision. http://www.dvp.net/news_details.asp?docID=262
This is great since this solves our problem when entering long descriptions on PO’s. Two questions though - since next control property is set to its own, users cannot use the TAB (oe enter)keys to move to next field on the form. Is there any way to solve this problem? Last word written on each description line usually tends to be split on two lines since system now uses auto enter and this does not wrap/move the whole word to next line. Any ideas how to go around this?
Try a solution in the OnInsert-Trigger and in the OnNewRecord-trigger
Any ideas like what? I did not understand exactly what do you mean by solutions?
I think that you can try to program the behavior in C/Side with the use of the named triggers and the REC und XREC variable. I am in doubt if there is already a programmed solution out there
This is hilarious! My colleague is on a vacation now and just before he went he made an adjustment in the Comment Sheet. Now the problem was that at the end of the line the input wasn’t switched to the next line automatically. After which I searched on this forum for answers. And I found an answer! And the author of the thread is the same colleague who caused the problem! [:)] Thank you Peter!
7 years later…
Same problem.
And again this post was helpfull! 