I use report with textbox (in Access 07) that should resize with length of text. I use the 'can resize' and 'can shrink' attributes. This mostly works, but on some computers the text box stay in 'original' size, as it appears on design view of the report.
I didn't find what could cause this, all computers have the same version of office (07), reinstalling office doesn't change anything?
So onto the questions. Any ideas how to avoid this?
Is there a way to adjust the size (height) of the textbox in report through access. Is there a way to determine the number of lines a text will take in some font and size other then dividing length of the string (using rich text) with some predetermined number.
Can you check the problem user's profile to make sure they have a printer installed?
I know it sounds like a silly answer, but I've seen odd things happen in Access Reports when no default printer is defined
Related
I understand that I can never exceed the width of a report body, but I have more report items than a (Design View) page can hold and I don't know what to do.
To clarify, what is currently on the Design View page correctly becomes a longer display view, and becomes multiple printed pages. Just what I want.
The problem is that I've run out of vertical design canvas and I don't know how to fix that.
Now that we've identified the PBI-Desktop tag was erroneous, the problem domain is SSRS Report Builder/PBI Paginated Report Builder doesn't give you enough space to craft your report.
The right but wrong answer is to go into the Property menu of the Body and there you can change the Size of the report.
Here you can see me manually increasing the size of the report body but it's easier/more precise to work with the property window.
Why it's the wrong answer -> You're designing a paginated report - one designed to be pica perfect on your page. Now we're stuffing a 21.875 inch body of a report into an 8x11 page piece of paper. Viewing of it might be ok but when someone clicks print, what happens? Is it going to squish all of that into a single page? Will Page 1 of the report really span N pages? It's been too long since I've worked with SSRS to that level of precision and I really don't remember but do test early if printing is a crucial aspect of the report delivery.
Outdated PBI Desktop/Service answer in case someone else needs it
In Power BI Desktop, click in the background and under Visualizations go to the Format tab. Change the default page size to custom and I could create a 99999 pixel tall report but I doubt that's advisable
I have a web app with a form in it. The form in turn has a select element with options containing a bunch of users' info, their names being set as the label/content of the option elements.
Now apparently one of the users' parents think it's fun to give their child a name with 3000 characters of gibberish in it.
I wouldn't want to make his life any harder than it is, but unfortunately I'll have to remove his account because the long name seems to introduce some interesting limitations on browsers that I didn't know about.
I started highly scientific testing using this fiddle with a few browsers in two computers and found out that
Chrome v50 (64bit) displayed a black box instead of the dropdown when the label length hit 1510
FF v46 refused to open the dropdown at all when the content length was 2716
IE v11 doesn't even break a sweat with tens of thousands of characters
Chrome v49 was the least fun of all. It rendered the whole window and all the other open tabs fully black so I had to close them all and start again. Didn't bother to find the exact limit for that
It seems though that the actual limits are much more related to the content width and not the length, as changing the character from "a" to "i" using proportional font affected the results.
The question: is there a reason Chrome and FF flip out with content of this size? Is there a specific limit on how long/wide the option's label can be (other than the subjective opinions about aesthetic/usable form inputs)?
After a Citrix upgrade, all my MS Access reports appear slightly bigger and several of them bleed over the margins into additional pages where a sliver hangs over.
It is not feasible for me to go through each report and manually resize everything in Design View -- several of them have already been compressed quite tightly. Is there no way to "fit to width"?
There is indeed a "Fit to Page" property.
Report properties -> Format Tab -> Fit to Page -> Yes
It is in my experience that I'm going to say that this probably won't be the universal fix you're looking for, and it might not even work. On reports that have bled over, I had to manually adjust each report. Of course I noticed this as I was developing them so it was not as time-consuming if I had to do 20 within a week, per se.
There are a decent amount of properties you can toy with, including Page Width, Auto Center, Auto Resize, etc.
Formatting can get very tedious. I'm hoping the default properties will work for you, but keep in mind that a manual fix may be required.
I believe your problem is related to the printer driver. Microsoft Access reports are constrained by the capabilities (printable area) of the printer driver assigned to them (either the default printer, or a specific printer, if chosen).
The unprintable margins of your printer, as defined by your printer driver affect how your Access report pages will be laid out when previewing or printing.
For example, if you have your default printer driver set to a laser printer, you can usually design a report with 0.25 inch margins on all four sides (top, bottom, left right). For this example, lets design a report that fills the page with 0.25 inch margins, and only takes one page.
Then, if you change your default printer to an inkjet and open the same report, you may find that the report is now wider and/or longer than one page. The reason is that in many cases, an inkjet printer has wider minimum left and right and/or top and bottom margins. Some inkjet printers can't print closer than 0.6 inches from the bottom of the page. So, your report which fit with 0.25 inch margins now is wider or taller than one page because the printer driver settings will take precedence over your report margins.
Unfortunately, with Microsoft Access, there is not a true "fit to page" feature, like Excel. I wish there were.
I would imagine that your printer driver has possibly been changed or upgraded and now has a narrower printable width. (i.e. previously the minimum left and right margins were 0.20 and now the minimum left and right margins are 0.25)
If you open a report in design view, then go to the Page Setup, set all of the margins to 0. As you type the "0" and exit each field, you will see Access change the 0 inch margin to the minimum allowed value for the current printer.
Unfortunately, the best advice I can give you is to design your reports with the margins of your "least capable" printer. The safest margins are usually no less than 0.3 inches for left and right, and no less than 0.5 inches top, and 0.6 inches bottom (to accommodate most inkjet printers).
You will probably have to manually edit each report in design view in order to fix them, OR change the printer driver.
I noticed that nobody addressed that your project is using MS Access on Citrix which is essentially a remote connection to a computer that users share (aka Terminal Server). As I recall there are special Office installation files that are required when installing Office on a terminal server. In part, the installer addresses how video and print drivers are used. I found this to apply to both displaying Forms and printing Reports. For Forms, in the end I had to apply finishing layout touches via the remote connection so that the video drivers metrics were saved with the form. For reports, there were two issues: The first is making sure that each report is set to use the 'Default Printer'. There is code available to walk the reports and set each to the Default Printer. The second was again finalizing each report's layout using the remote connection and the default printer installed on the remote connection. However the workaround to this is to install an local generic printer driver (aka an basic Epson Dot Matrix driver) and final each report for that printer. When deployed most modern printers understand the metrics of the basic printer driver. Note that code could be used to walk the list of reports, open in design mode, change a setting and the Default Printer then save. This could be enough to reset each report's configuration to match a Citrix or Terminal Server deployment.
I hope this helps!
Ken
Developing MS Access custom applications since Version 1.0 - Our first version had a box's serial number of 0000071 which we acquired as a give-away during the launch at Comdex Las Vegas.
Background:
I am creating an application in Ms-Access that is to be launched on a multi-user platform - This means many screens and many different resolutions etc.
Question:
Is it possible to have my application that automatically adjusts to the right size of the screen/resolution and the font size to be proportional to that of the % increased or decreased?
Similar to my answer here, yes, you can use the On Resize event of a form to move controls around, change the size of subforms, and perform other similar operations. Those adjustments are applied to each individual object, so the coding would be somewhat tedious and a bit "fussy", but it can be done (at least to some extent).
The font size will not automatically change based on screen resolution in any version of Access, but starting with Microsoft Access 2007 you can use new properties of controls to make them stretch, shrink or move based on the size of a form (described here)
Try using the VBA code in this answer to see if it gives you what you want. It works basically the way that Gord Thompson recommended. When the form is resized, all the controls and the text on the form will be proportionally resized too so that it looks the same no matter what size the window is, or what the user has their monitor resolution set to.
I have two textboxes arranged one immediately above another in the detail area of an Access 2010 report. They both have Can Grow set to Yes, as does the detail area itself.
When both textboxes have had to grow to accommodate their contents, and the text in the bottom textbox is long, its text gets truncated. How can I address this?
Yes, this is a known bug. It's based on the font and printer. Another user claimed that switching to Arial fixed the problem. His issue was with the Calibri font, while mine was with the Tahoma font.
My experience was that it depended on the printer as well, as my client would get this bug with one printer, but not another, using the same computer.
Switching to the Arial font worked for both of us. Except for the testing already mentioned here, there's no list that I can find of which fonts are buggy and which ones work.
Is the format of your text boxes by any chance set to Rich Text?
If yes, this is a known bug. So far, the only workaround we have found is to avoid rich text in reports. Text already stored as rich text in the database can be converted to plain text by using the PlainText method (i.e., set the ControlSource to =PlainText([field])).
We are suffering from this issue as well, so if you found any other workaround or solution, please drop me a comment.
I tried all suggestions I could find here and elsewhere: changing fonts, printers, verified PlainText, etc. But nothing fixed this issue.
Here's what finally worked for me:
Open the report to the Print Preview view.
Click on Page Setup on the ribbon.
Click the Columns tab in the Page Setup window.
In the Column Size section, click the Same as Detail box.