Forms 6i to 10g [message #585278] |
Thu, 23 May 2013 07:42 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](http://www.gravatar.com/avatar/a7f9d01787d766ca3ecf0d633906c5f0?s=64&d=mm&r=g) |
sankalputtara
Messages: 53 Registered: January 2011 Location: Bangalore
|
Member |
|
|
Hi,
While migrating Forms 6i to 10g i have come across one unique behavior
1. In Forms 6i- Suppose we have a text item of datatype char and length 5.
Now copy a text of 10 characters 1234567890 and paste it in the text box and it will automatically trim and take
1st 5 characters(12345) and show in text box.
2. In Forms 10g- Suppose we have a text item of datatype char and length 5.
Now copy a text of 10 characters 1234567890 and paste it in the text box and it nothing happens. Character length
is more than 5 then it does nothing.
I need to implement the 6i behavior in 10g. Any suggestions (apart from validation trigger). Any property available?
|
|
|
Re: Forms 6i to 10g [message #585514 is a reply to message #585278] |
Mon, 27 May 2013 03:21 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](http://www.orafaq.com/forum/images/custom_avatars/72104.gif) |
Littlefoot
Messages: 21818 Registered: June 2005 Location: Croatia, Europe
|
Senior Member Account Moderator |
|
|
From my point of view, Forms 10g fixed a bug in Forms 6i version which allowed you to enter value longer than item's maximum length allows. Yes, it was smart enough and trimmed the value, but that's also misleading behaviour because you weren't warned that it happened. After you have saved data and thought that everything's in there, you'd - some time after - perform query and wonder what happened.
It is obvious that you can actually SEE what happened in a 5-characters long item, but that could have been an item that allows, say, 200 characters, but you displayed only first 20 of the whole item. You wouldn't even know that the rest was trimmed (because you couldn't see it).
Finally: no, I wouldn't know how to implement it (apart from using a trigger).
|
|
|
|
|
|