I am trying to search how to make a expendable field in acrobat. Means i have some data and i want to organize it in a way so that on first glance only important data will be shown but additional information can be accessed if you will click the near by button.
For ex:-
page have this information.
This year's whole production is 200 units. list of products
Total consumption is 190 units.
but after clinking "list of product" it will show the page like below
This year's whole production is 200 units.
list of products
X type products = 50 units
Y type products = 100 units
Z type products = 50 units
Total consumption is 190 units.
Any comment or suggestion is welcomed.
Thank you.
This is possible.
According to Adobe Propaganda, you would need an XFA form for that (created with LiveCycle Designer). There you can specify a field to be growing according to its contents.
However, it is also possible to do it with PDF forms (using AcroForms). You may have to take some precautions, but it can be done.
One of the field properties is rect, which consists of the coordinates of the top left and the bottom right corner point of the field. With this you can programmatically change the size of the field.
In your case, you would have to figure out by how much you would have to stretch the field to properly display all the additional information; you may have to analyze the additional text at runtime and then determine by how much you have to stretch. You will also have to refresh the field value after changing the field's size.
And that's about it.
Note that this feature works only with PDF viewers understanding Acrobat JavaScript.
Related
I am trying to extend the maintenance view(sm30) of a table, so that all the fields of a table are shown without paging. So the current look is:
Now I need to show all the fields of the table without scrolling to the right. Does anyone know how is this done?
Thank you all in advance!
The Table maintenance generator has a number of annoying weaknesses.
Generating overview lists with a width of 80 is most obvious one.
So if you are generating maintenance views for your own tables, it is easily improved.
Generate your maintenance screen .
Drill down to the generated dynpro.
You will notice on the screen attributes it is only 83 byte wide !!!! WHY ???
That goes all the way back R/3 version 2.x in the early to mid 90s.
So just make the width 250 chars.
Then goto Layout.
Grab the lower corner and drag out to 250 char wide.
when you are done, the occupied width will reflect the change
Now activate.
The next time you use the overview screen you will see 250 chars of table.
I often adjust the width of some fields while doing this in the case they are
are unnecessarily large.
EDIT: NOTE about regeneration.
If you regenerate your screen/s , you will need to redo the changes.
I'm placing hundreds and hundreds of boxes in dozens of carts with an optimization algorithm.
Problem:
How the boxes fit in the carts should be presented to the Access user visually and in print, and it should support moving individual boxes to other cart, by supplying a box ID and target cart ID and redraw. More ideally, via drag-and-drop.
What have I tried:
Rectangle objects on a Form. Hits the object limit after a few hundred boxes.
DuckDuckGone. Looked at Canvas and CanvasShapes. They seem to not be canvases proper?
Looked at external tools to say, compose a PDF. It wouldn't be interactive, though, and data would have to be passed as XML or similar.
Question:
Is there a way to draw say, 1000 rectangles in any type of window (Form, Report, etc.) in Access 2013 using VBA?
The rectangles are coordinate-based, so that it can't be presented as a table; you wouldn't see the physical dimensions of the carts and how the boxes fit in them.
In reports, you can, with the Report.Line Method.
But it will work (AFAIK) only in Print Preview and Print, not in Report view. So no interactivity whatsoever will be possible.
But I'm pretty sure it's your best option in Access.
The number of pages displayed when viewed in ReportViewer and in exported PDF are differing.
Eg: 50 records are shown in one single page of Report Viewer. But when Exported to PDF 45 reords come in page 1 and the remaining come in page 2.
Soution Tried:
1)Removed Top and Bottom Margins.
2)Reduced "Interactive Page Size" to match the page count.
But it is not consistent, as it is behaving differently with different number of records.
Can anyone tell me how should I proceed to achieve sync between the ReportViewer and exported PDF ?
Thanks
Short answer - you can't do what you are trying to do: the different renderers handle pagination differently, but appropriately for their output.
The HTML renderer is optimised for screen-based reading and generally allows more content per page than the print renderer does as the print renderer is constrained by the paper size that it formats to. Thus the HTML renderer allows more content on fewer pages for a better browser experience whereas the print and PDF renderers have to conform strictly to the page length.
The best illustration of this is the Excel renderer - the Excel renderer renders the entire report onto a single worksheet in most cases (for reports with grouping and page breaks set on the group footer it will render each group on its own worksheet). You wouldn't want the Excel renderer to artificially create worksheets to try to "paginate" your report or to put it all in one worksheet but insert the header into the spreadsheet rows every "page". It does the appropriate thing which is to include all the data in one big worksheet even though that may be logically thought of as one big "page".
The HTML renderer page length is determined (more accurately, influenced) by the InteractiveHeight attribute of the report (in the InteractiveSize property in the Properties pane for the report). However, the interactive height is an approximation rather than a fixed page break setting and your page breaks may still not conform to the print version even if you set InteractiveHeight to the same length as your target page length. This is because the HTML renderer will vary the page length to group the data together better so the interactive page breaks happen around about, but not always exactly, where the interactive height is set.
This is what is happening in your scenario where the report viewer shows 50 records on one page but the PDF has 45 on the first page and 5 on the second page. The report viewer is making the decision that since there are only a few records left to display it will just include them all on the one page rather than force the user to scroll even though the interactive height will be exceeded. Thus you get a better user experience but a variance in pages between renderers. The important thing about the report is the data and the experience with working with that data in that renderer, not that the pages are the same length no matter how you look at it.
See this discussion of rendering behaviour for more information on why what you are trying to achieve isn't achievable. Just educate your users that the browser pagination is optimised for their viewing pleasure.
I have some forms that I need to add expanding text boxes to.
I already have Multi-Line selected. And yes the scroll-bar appears when field is full and you keep entering text. However, when you go to print, it doesn't print out the full text.
I know in Adobe LiveCycle you can make dynamic forms, that bump onto the next page. I have done this, but you lose so much functionality in LiveCycle. To be dynamic you lose the ability to position objects without using tables and therefore doing designs and graphics are not as easy.
Has anyone found a way to do this in Adobe Acrobat X Pro?
At this point, I think it would be easier just to convince people that a web form is much easier to update and style any way you want with print CSS stylesheet.
Thanks for any suggestions.
To be dynamic you lose the ability to position objects without using tables and therefore doing designs and graphics are not as easy.
That is not true. A form being dynamic or not has nothing to do with having flowed or positioned content. A static form renders once on the server, a dynamic form can be re-rendered on the client and thus is able to reflect layout changes like hiding objects or altering heights of objects (more info).
With either form type you can have both positioned and flowed content. The trick is to divide your form into subforms according to the structure of the data you want to display (tutorial).
To let the text field grow automatically with the amount of text, enclose it in a subform with flowed content, allow multiple lines and enable "expand to fit" (or "auto-fit).
I created a report in reporting services 2005 with a report page size of 14in x 8.5in. The report looks fine in the reports manager and also in the report viewer. The issue is when I export the report to PDF, the page size in Adobe states 14 x 8.5 in but when you hit the print button, it selects Letter size (8.5 x 11) instead of choosing Legal size (8.5 x 14).
If you then click on 'Choose Paper Source by PDF page size' or change the paper source to legal, the report prints out exactly the way I wanted it.
Does anyone have a solution to this? Thanks in advance
I remeber we had a similar problem a few months ago with Reporting Services 2008 (not 2005).
I think the solution was to "force" the values of Width and Heigth for the desired amount, regardless of the selected item in "Paper size" dropdown box (in Report Properties -> Page Setup)
In our case, we wanted to print in A4, so we set width = 21.59cm and height = 27,94cm, even if selected paper size remains as "Letter".
Just i choosed the Report Properties -> Page Setup --> Paper Size is A4 , then it was get working fine for A4
- GAM SKJai (L&T ECC)
I've had this problem too, and I've never found a satisfactory solution. SSRS doesn't offer much control over print settings in export formats (like fit-to-one-page-across in Excel).
One work-around would be to roll your own interface, intercept the PDF file, and update the print settings before serving it up to the user. Could be a lot of work, and how would you know the intended page size? You could always parse the RDL file for the page size settings, and that would be a correct solution, but damn if that's not a lot of extra work.
EDIT: check the page size under page setup, as pv2008 suggested.
Report Properties --> Interactive Size set it to whatever you want and it stays, even after closing and reopening the report. I exported pdf and it retains the size. You can check by right clicking on the pdf and go tot properties.