I was moving tablixes around my page and ended up with some stuck inside the header row of another like so;
It definitely isn't overlaid, I have that going on with my other tablixes at the top of the page, as intended. These have somehow merged so when I try to grab the corner handle I have to click it multiple times to turn into the move handle and then only the main table is moveable, I can't grab and move the tables that have merged into the bigger one.
It's stopped the report from running and I can't find a way to take it out, I can't undo past a certain point either as I saved and rebooted my PC before I realised it was this problem that was causing my errors.
Does anyone know any way to take the damn things back out or do I have to redo hours of work? :'(
Refer to the screenshot below.
Click somewhere inside the nested table. You should see the column/row outlines like in the picture
Left click the top left corner handle
Ctrl-x to cut and then ctrl-v to paste somewhere else on the page.
In a broader context, you can use the right-click and then Select option to select any item that is layered with others.
Related
I am not really experienced with coding so I apologize in advance if this is a stupid question with an obvious answer...
I use a google sheet to keep track of things at work, and my employees use it multiple times a day. They will either type one of three phrases into a certain cell on a row, so I have created buttons using the drawing feature that they can simply click, which will insert the appropriate text into the highlighted cell.
Once this text is inserted into the cell, I would like to add something to the end of the function that automatically selects the next adjacent cell in the row (to the right) so they can continue typing in. Currently, once they click the button to insert text into one cell (e.g., B23) they have to use the mouse to manually select C23 before typing into that cell. For some reason you cannot use the right arrow key or tab key on the keyboard to move over, so I am wondering if there is a way to add the selecting process into the script (or even a workaround for allowing the tab or right arrow keys to work).
I realize this may seem like a tedious question and folks may think it is awfully lazy of me to ask for a more efficient way to move over to a cell than using the mouse, but my employees use the sheet hundreds of times a day, so I'd really like to maximize the efficiency for them to make it as easy and convenient as possible. Inputting data can be tedious enough, so I am trying to simplify things and make it as least painful as possible :)
Thanks so much!
There are several ways to select the cell at the right. One way is to use offset(rowOffset,columnOffset):
range.offset(0,1)
You are correct. When using a button the focus stays in the button when it is clicked. After some trial and error, I think I found a way that will work fot you. I created a html sidebar that is opened from a custom menu. Once opened, you can leave it opened, HTML allows control over the focus using 'google.script.host.editor.focus()'. Then you can type in the cell. Attached is my sample spreadsheet you can copy and try. Let me know if you need any help changing the button names or text. Sorry my first try didn't work correctly. https://docs.google.com/spreadsheets/d/1KlNSJnZDNIb2chUK3SlKJg79VNIrsAbIbUvHyLwTLWk/edit?usp=sharing
I have six sub-reports and I would like to arrange them as shown below.
The idea is to show the top one in first page and last two in the second page. When I tried, each report appeared in individual page. Putting first 2 reports ( side by side) in a rectangle and inserting page break after also did not work.
Each sub reports were generated using matrix.
Any suggestion would be greatly appreciated. Thank you
You would need to put the reports inside of a 'Rectangle' object and limit page break scope there. So if you want the last two only on a new page, put just those two inside a rectangle. Go into the rectangle's properties and set a page break.
I have two list boxes in a form. One of them is bigger than other. Smaller one was placed at the back of bigger one. I tried position > bring front for smaller one and position > send back for bigger one, but didn't work. Also, tried to change Tab index in Other menu and wrote codes Me.Repaint and Me.List.SetFocus but they didn't work neither. Is there any way to change to bring smaller list front?
Right clicking on the listbox and select Position -> bring to front should work (in Access 2013), but the layout of two listboxes are a bit messed up then.
A Listbox is not ment to be on another listbox, and I cannot imagine why you want to do this. What are you trying to achieve here?
I can't seem to figure out what i'm doing wrong here...thought I might be overlooking something not common as the cause for this so I decided to post a thread.
Report is set for 8.5 x 11 with .25" margins on all sides
Body is 7.89 x 2.90 with all padding set to 0 for report items.
I use a footer but it is the correct width.
I use a hidden detail row that expands from my normal detail row, but the overall width is still less than 8".
I attempted to make a new report and copy the reportitems over so that if I had made a configuration issue I might find it. But the new report behaves the same as the original one I did.
ConsumeContainerWhitespace is True. The tablix on my report is the only item that can page break after and that option is unchecked.
I changed my footer to not appear on last page and it still leaves a blank page for me.
Any thoughts?
I know it may sound funny..but i have tried this many times whenever I got some issue like this..and I resolved the issue..
sometimes the report object may extend in length by very small inch..and you cant find out that..
What you can try is:--Give some background color to the object such as tablix and then render the report in some format like PDF..if its length giving you next page then the some part of color you can see on that next(blank) page..from that you can get idea about the size of perticular report item which is causing the issue.
I hope this will help you..
I had to throw out the current copy of this report and recreate it. 2nd time through I didn't get the extra space causing the extra page. I wish I could have figured out what caused it because the hand grenade approach is not the one I always like to take.
I found that I can write code just by typing everything or activate element, then click for example OnClick property and write code to between the sub-end sub lines.
One person I met said that one has always use mouse and select the property in which you want to write the code, as it might write something else to some files such that the code won't work.
Is this correct or are those two ways to write code equally good? I'm using Access 97.
The short answer is you CAN do it that way. But it doesn't mean you SHOULD.
With a little experimentation I've found that you can type in event subs directly in the code window, and their creation will be reflected in the properties window. This might not have always been the case in older versions of MS Access.
You can also create them by selecting the Control in the code window's top left pull down, and then selecting the event in the top right pull down.
Why would I choose to use the Code Builder (or at least the second option I provided). Because it prevents you from making mistakes. Both in the name of the control/event and in accidentally creating duplicate Subs. Both of which could be frustrating when debugging your application - how long could you spend looking for a bug because you added an extra "S" to an element name by accident. If you follow through from the properties window, you are guaranteed to be working on the right Sub and that it will be spelled correctly.
Note: I've also found that you can delete the entry in the properties window, but it leaves the code behind in the code window. So to make sure it is really gone, you do have to go into the code window and delete the Sub there.
That's not to say that I never do anything directly in the Code window like that - if I've renamed a control, I'll often update the name in the code window. But then I'll go back through the properties window to verify that I've re-connected the subs properly.
"Look, I'm running with scissors!"