Calendar LOV too small

Greetings,
Okay so I attached teh stndrd20.olb and calendar.pll to my form and subclassed the calendar object group and created a button with a when button pressed trigger to issue the date_lov.get_date function. The calendar pops up but it's tiny. The data blocks created for ex. the date button block has buttons with a width and height of .032 and .028 respectively. This makes the calendar non-functional as it can't be seen. How can I resize this or specify the class to create objects a little larger so they can be seen? Thanks!

Thanks for the reply, so I checked and it appears the calendar was developed with measurements in pixels but our form uses a coordinate system in inches. I changed the form to pixel so the calendar looks great however we use a toolbar that's common to all our forms created in inch measurements so it's now huge. If I change the toolbar to pixel sizes I'll have to change every form in our application to pixel and that's over 120 forms all under change management. Is there any way to change the calendar to inch measurements in the class so it can be used in our forms or can teh coordinate system be split and different for different windows of the same form?

Similar Messages

C7 after belle update calendar fonts too small

After I updated to Belle I am experiencing some problems reading the calendar appointments. When expanding an appointment in calendar view to look at details font is very small. I think this is a persistent bug because neither in edit mode fonts get larger. Pls fix this. Best Pasha

Hi Pasha_NC7,
It can either be that the update hasn't been installed properly, or that the font size that has come with Belle is too small for your liking. Try to reinstall Belle with Nokia Suite and see if this makes a difference. If it doesn't then you won't be able to change it to a bigger font, but it's worth a shot.
Let me know how you get on!
Iris9290
If my post has helped you in any way, please accept it as a solution or click on the white star, so that other users will be able to benefit from it too.

TS1347 Just downloaded ios7 on my iPad2. Hate that I cannot see the items in my calendar. The letters are way too small and are grey in color. I need the fonts to be dark and very defined...I have health issues-poor vision.

Just downloaded ios7 on my iPad2. Hate that I cannot see the items in my calendar. The letters are way too small and are grey in color. I need the fonts to be dark and very defined...I have health issues-poor vision.

Settings>General>Accessibility>Increase Contrast
Settings>General>Accessibility>Bold Text
are some settings that may help.
There are other settings there ...they may not be to your liking but try them all anyways.
But that's about all you can do for now...except to voice your opinion to Apple here:
http://www.apple.com/feedback/ipad.html

Character string buffer too small (select list query based LOV)

Hi,
Using the select list query based LOV with a select witch is too big, you get this error.
report error:
ORA-20001: Error fetching column value: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
When using the Popup LOV query based LOV) then it works nice.
Can that be solved somehow?
With the Popup LOV the return value is displayed in stead of the description.

Hi Andy,
How do I incorporate your suggestion on a report ?
Example : I have
select apex_item.display_and_save(1,column1,5) col1,
apex_item.display_and_save(2,column2,5) col2 ,
apex_item.popup_from_query(3, emp_name, 'select user_name, name empname from table2) col3
Table 2 is a long list , and I'm getting string buffer too small due to this.
Your suggestion with HTP is good but I'm not sure how to implement it for reports as I'll like the user to change the values with the select_list.
I'm not using forms as they want mulit-record on the same page.
Hope to hear back from you soon.
Thanks very much.

Bug: Report Column based on LOV character string buffer too small error

When using a column type of "Display as Text (based on LOV, does not save state)" with a result set that is rather large causes a character or string buffer too small oracle error.
See the below page for an example.
The example page below has a single report off a table called "HUGE_TABLE" which has two columns: display and code
Code contains a number between 0 and 100000.
Display contains the number in code appended to a block of text.
When I display the report with no Display As Text (based on LOV does not save state) it displays fine.
If I make the "Code" column display as text based on LOV and make the LOV
"SELECT display, code FROM huge_table"
I get the error you see on the page.
http://apex.oracle.com/pls/otn/f?p=32149:1
Thanks.

Thanks for your help Scott.
So from what I've gathered from my own tests and the discussions you linked me to the LOVs based on SQL queries are being converted into "static LOV" strings before being used.
As such they are limited to the PL/SQL VARCHAR2 max size of 32767
Which means given the static reduction of the string 'STATIC:' that we have 32760 characters left.
Which is where your SUM( LENGTH( display ) + LENGTH( return ) + 2 ) comes in.
In short, if:
sum( length( display ) + length( return ) + 2 ) + 7 > 32767
would evaluate to true then you have a problem. :)
I'll use this to track down my problems and switch them over to inline queries.
Thanks.
Cheers,
Joe

Calendar event font too small

New events I create in calendar have a font too small to read. How do you change the front size?

I'm having the same issue. Did you get an answer? Seems that calendar entries created within Outlook on my laptop are fine, but entries created on my iPhone have a very tiny font. changing default font in "Settings - Display and Brightness" does not help. Thanks.

LoV - popup window too small

Hi all,
I'm using Oracle Forms Builder 10gR2. I have a LoV attached to a button but when the user open it - the popup window which appears is too small and customer has to enlarge it.
Any ideas how to set it larger? Maybe in property palette or other option i have to define?
Thanks in advance,
Bahchevanov.

You can set the width and the height of the LOV plus their x and y position in the property pallette at design time.
cheers

LOV - PL/SQL: numeric or value error: character string buffer too small

I have a field set to 'text field with autocomplete' and now that the data that is used for the LOV has increased dramatically it returns the following error 'ORA-06502: PL/SQL: numeric or value error: character string buffer too small'. Through trial and error I determined that if I restricted the number of rows returned using rownum < nnn then it would work. I then determined that I could use the trim and substring functions and remove the rownum restriction and it would work. Below is the LOV query. I have seen a couple of other posts similar to my problem and one of them asked if there was a way to increase the buffer size, but it was never answered. Is there a way, such as a parameter setting, that I could increase the buffer size for LOVs?
select distinct substr(trim(item_requested),1,50) d
from consolidated_components
order by 1
Thank you.

Hi Scott
Thanks very much for jumping in here.
No, I didn't use the wizard to create the page. It was a manual operation but to tell you the truth the page has been changed so many times as I was working on different functionality and appearance that anything could have happened. I ended up having to manually create row processing processes and delete other processes, creating and hiding buttons, changing the way I'm passing item values, etc. I realize regardless of what I do as a developer the software should be able to handle all changes through it's interface but I've been in this business long enough to be realistic.
I also could have done something blatantly stupid as I continue to learn this product. For those of us not yet totally comfortable with all the web development technology, Javascript, AJAX, etc., but are asked to develop applications that work best using those technologies sometimes we make elementary blunders.
Thanks very much for your help. It is indeed appreciated.
-gary

Font in Menu Bar and Drop Down list way too small

I just tried PSE 10 and was very surprised to see that Adobe did not address the problem with the font size being way too small in the menu bar and drop down list. I cannot possibly read the font - so the program is basically unusable. I am using a new 17inch laptop. Is it possible that after all the complaints Adobe didn't fix this problem in PSE 10? Are they even working on it? I love the program but unfortunately I am going to have to switch to something else because there is no way I can read the font and thus cannot use the program at all. Very, very disappointing. Hopefully they are working on a fix???

Photoshop CS5 Essential has preferences that offer users the opportunity to adjust menu bar background color as well as font size. For example,
"UI Font Size
If you find that Photoshop's interface text is a little too small for comfort, you can increase its size by changing the UI Font Size option to either Medium or Large. And no, this option isn't just for old folks with poor eye sight. Working on a very high resolution monitor can make Photoshop's interface text appear very small. Personally, I like to set my font size to Large which I find helps to avoid eye strain. You'll need to close and then re-open Photoshop for the change to take effect:
Change the font size to increase some of the text in Photoshop's interface.
(From an article by Steve Patterson at http://www.photoshopessentials.com/basics/cs5/preferences/ .
Why not Photoshop Elements? ?
Lensw

Report error:ORA-06502:character string buffer too small. urgent!!

Hi guys,
My APEX version is 3.0.1.00.08, my application run on my test environment, but on PROD environment, it raised the error:
report error:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
In this page, on the left is a tree, the right side is a tabular form, when I click one tree node, it will pass the current node id to the form and the form will display the children data. When I click some tree node, it will raise the ORA-06502 error, but when click some other nodes, it is correct. I don't know why. And on my test environment, it has no this error, the test environment has same version with prod environment, only has less data in database. Could you help me???
I searched in forum, someone says it's LOV problem, if it's LOV problem, all the nodes should have error, why click some nodes are ok?
Thanks !
Jessica

I don't think it is related only to the number of rows but also to the content of the rows. So, counting only the number of rows doesn't say anything about if it is going to work or not. My question: can't you filter those entries? Making a choice between 250 entries in a tabular form isn't a simple task. Using popup-key LOV instead would also be a solution. However, if you use popup-key LOV be aware of the fact that you need two index numbers for those.
Denes Kubicek
http://deneskubicek.blogspot.com/
http://www.opal-consulting.de/training
http://apex.oracle.com/pls/otn/f?p=31517:1
-------------------------------------------------------------------

Yosemite fonts too small for middle aged eyes

I just updated my desktop to Yosemite and am wishing I hadn't - the designers clearly don't have a clue what happens to normal eyesight in middle age. I am NOT vision impaired - just a little bit short-sighted (-1.5) and a little bit long-sighted (+1) and a little bit astigmatic, with up-to-date glasses that correct my sight properly. I am nonetheless finding using this new OS on my new 1920x1080 (non-Apple) monitor, which worked perfectly with Mavericks, absolute torture - all the text in menus, settings screens etc is just much too small for comfort, at least in the chosen font. In some apps I can use Cmd-+ to increase the font size, but there seems to be nothing I can do about the font sizes in Finder, Preferences etc
I have read the threads about the reasons and ways to mitigate the problem, and have increased contrast and reduced transparency in the Accessibility settings, and am considering running the script to change the default font back to Lucida Grande. But my point is that I have perfectly normal eyesight (for someone of 53) and have never had any screen problems before, so I shouldn't need to be using the Accessibility settings. I know it is fashionable among designers to create lots of blank white space, but white space doesn't compensate for illegibility!
I can see from all the threads on this topic that I am not alone. So please Apple, sort this out - usability must come first - and not just for the under 30s!

Even iBooks on MBP Retina !?
I love the iBooks app and use it specifically because of the "Night" appearance option, which turns the page background all black and the font white (similar to inverting the display). Fortunately books' font sizes remain adjustable as big as I want, but - I can no longer see page information (current page number and number of pages left to read) at the bottom of each page. The page information is barely visible (appears like small dark grey foggy font on a black background). This is very likely also the result of the Yosemite font fiasco. Not an issue when reading books in "Night" appearance on the iPad, (they didn't break it yet yet in iOS).
"Digital Books without page numbering information"!
A Huge design fiasco.

Is 3.5" screen too small?

I love these new displays and all, but I'm starting to think 3.5" is just too small. It's a very introverted experience. I'm using a Dell Streak now with a 5 inch screen, it's about the same thickness as the Iphone4, but with a much bigger screen. I was planing to have both Iphone and an Android phone, but there's no getting around this small screen problem now that I've tried something bigger. will Apple ever develop a larger screen? Even 4 inches like the EVO is better.
Please no Android vs. Apple debate, I'm wondering if 3.5" will be extinct soon and Apple will ever come out with a 4 or 5 inch phone. They've already achieved the highest resolution needed so the only way to improve now would be to make the screen bigger, right?

I had a 3GS and I loved it but I upgraded to the HTC HD2 after 6 months just for the larger 4.3" screen and gave my 3GS to my mum, can't get her off it
I mostly use my phones for sat nav use so the large screen is amazing.
It's much thinner than the 3GS and very quick and not that much bigger than the 3GS because HTC made the screen corner to corner unlike the massive bezel on the iPhones.
I never found the size to be a problem and fits into my pockets just fine, can even just about use it one handed.
Have owned it for about 6 months and love it, very clear and crisp screen but I do miss my 100 iPhone apps, many that I paid for.
I do have an iPhone 4 32gb on the way to replace my HTC HD2 once Apple decide to ship it, should be here around the 14th July, hopefully much sooner.
Can't wait to play with it, amazes me that they squeezed all the technology into something even thinner than my already very thin HD2
Will really miss the 4.3" screen though, shame Apple didn't use a 3.7" screen at least. For me 4" and 4.3" is the sweet spot.
Message was edited by: Radeon123

Checkbox Item: character string buffer too small (APEX 4.0. - 4.2.)

Hi all,
I'm currently running the Oracle Application Express 4.0.2 on the Oracle DB 11g and thinking about the APEX upgrading to current 4.2. version. We have there quite big application used by the inernal employees so prior I need to test, if the migration will work.
I installed the new server with database and the APEX 4.2. and import the current application. Everything seems to working good except few checkboxes, which returns me the error: "ORA-06502: PL/SQL: numeric or value error: character string buffer too small."
LOV (Source) Code of Checkbox Item:
SELECT email as display_value, id as return_value
FROM users
WHERE <some conditions>;
In the current version 4.0.2. I get the checkbox item (total count of the rows approx. 650), but in the 4.2. I get this "string buffer too small" error and the page could not be rendered (if I add to the same query limitation: "rownum<242" it will display the item).
Could you please help me with this issue? Any idea, what I should set up in the new APEX to get the same results or you see there any limitation, why it does not work in the new version, but in the old version the same SQL works fine?
Thank you all in advance.
Regards,
Tomas.

1007462 wrote:
Hi all,Welcome to the forum: please read the FAQ and forum sticky threads (if you haven't done so already), and update your forum profile with a real handle instead of "1007462".
I'm currently running the Oracle Application Express 4.0.2 on the Oracle DB 11g and thinking about the APEX upgrading to current 4.2. version. We have there quite big application used by the inernal employees so prior I need to test, if the migration will work.
I installed the new server with database and the APEX 4.2. and import the current application. Everything seems to working good except few checkboxes, which returns me the error: "ORA-06502: PL/SQL: numeric or value error: character string buffer too small."
LOV (Source) Code of Checkbox Item:
SELECT email as display_value, id as return_value
FROM users
WHERE <some conditions>;
In the current version 4.0.2. I get the checkbox item (total count of the rows approx. 650), but in the 4.2. I get this "string buffer too small" error and the page could not be rendered (if I add to the same query limitation: "rownum<242" it will display the item).
Could you please help me with this issue? Any idea, what I should set up in the new APEX to get the same results or you see there any limitation, why it does not work in the new version, but in the old version the same SQL works fine?The total size of the HTML generated for an LOV-based item in APEX is restricted to 32K (this limit applies to every version). Why you are hitting this limit in the new instance may be due to differences in data or the database configuration (e.g. character set) rather than changes introduced in APEX.
Is the data exactly the same? Is the database configuration the same? When you limit the number of rows so the checkboxes are displayed and view the page source, is there any difference in the HTML used to render the checkbox form elements between the two versions?
That said, from a usability perspective 650 LOV options is rather a lot, and your application may very well outgrow this limit naturally in any version of APEX as more users as added. It is probably worthwhile thinking about other ways to display these options.

HTMLDB_ITEM.POPUP_FROM_QUERY - character string buffer too small

I am creating a updateable report with a popup_from_query item on a table with a high number of columns (40 columns) where every column should be displayed as a popup_from_query.
I get the following error message when running the page:
report error:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
*** It seems the longer the column list gets, the shorter the p_lov_query parameter could be.
- Region 1: If you use only one column, your lov query fails with a statement that is 807+ characters. (if you use 806 it will work without an error).
- Region 2: If you use only two column, you will fail just with a value of 800.
- Region ?: I have 40 columns, now my query fails of about 30 charachters.
* Region 1:
select
htmldb_item.popup_from_query(5,'x',
'SELECT distinct '||COLUMN_NAME||' d, '||COLUMN_NAME||' r'||
rpad(' ',807,' ')||
' FROM '||TABLE_NAME||' order by 1') xxxxxxxxxxxxxxxxxxxxxxxxxxxxx1
from all_tab_columns
where rownum < 2
* Region 2:
select
HTMLDB_ITEM.POPUP_FROM_QUERY (
44, 'x',
'SELECT distinct '||COLUMN_NAME||' d, '||COLUMN_NAME||' r'||
rpad(' ',800,' ')||
' FROM '||TABLE_NAME||' order by 1',
least(DATA_LENGTH,60),2000
) xxxxxxxxxxxxxxxxxxxxxxxxxxxxx1,
HTMLDB_ITEM.POPUP_FROM_QUERY (
44, 'x',
'SELECT distinct '||COLUMN_NAME||' d, '||COLUMN_NAME||' r'||
rpad(' ',800,' ')||
' FROM '||TABLE_NAME||' order by 1',
least(DATA_LENGTH,60),2000
) xxxxxxxxxxxxxxxxxxxxxxxxxxxxx2
from all_tab_columns
where data_type in ('VARCHAR2')
I have set the region to: Use Generic Column Names (parse query at runtime only)
Has anyone some suggestions or workaround for updateable reports with a lot of columns where popup's are needed?
Thx Willi

Hallo,
Thank you a lot for that hint. But if this would be the case, why does Region 2 work then?
Any further comments are welcome.
Thx, Willi
P.S.: I had reached the 2000 items (<input>) limit, but now only display less 2000 items on the page: "Your browser sent a request that this server could not understand.
mod_plsql: /pls/htmldb/wwv_flow.accept HTTP-400 Too many arguments passed in.
Got 9016 parameters. Upper limit is 2000"

Vista & Outlook 2007: Sync with second XP & Outlook 2003 - The passed buffer is too small for the reply data

Dear Community,
I'm synchronising my T3 with two PCs. One with Vista & Outlook 2007 and the other with XP & Outlook 2003. Both with the latest conduit & Hotsync Manager versions installed for each OS based on the availability on the Palm Website.
My problem is that when I synchronise the T3 with either PC and then try to sync it with the other I'm receiving the following error message for the Calendar:
Outlook Calendar
The passed buffer is too small for the reply data.
OLERR:0D-0008
OLERR:0D-0004
OLERR:0D-0001
- Slow Sync
Outlook Calendar synchronization failed
The second time the sync is successful but takes a long time and the actual problem is that it creates duplicates for records previously changed on either PC - but with a sync in between those changes, i.e. no conflict in the sense that the same record was changed in both environments since the last sync. I have configured the conflict handling to establish a hierarchy PC1-T3-PC2 but try to avoid them by synchronising as often as possible.
Has anyone come across that problem or any ideas? Can you somehow adjust the buffer size for the sync? I have been using Lotus Organiser & then the various Outlook versions for a number of years.
Thank you
Rainer
Post relates to: Tungsten T3
Post relates to: Tungsten T3

As they say on TV, "Doh"!!!
I figured out the problem. I started the Sync tool, selected "Settings", then "Mcrosoft Outlook" tab and then "Select Folders" button. I browsed to the proper folders in Outlook (Calendar, Tasks, etc). Select OK enough times and retried the sync.
It worked.

Calendar LOV too small

Similar Messages

Maybe you are looking for