I have pop-up form for data entry. The form has a subform on it that is surrounded by blank cells of equal sizes similar to padding. (Why not use padding instead? Because I want to add functionality to those cells later on). When I view the form in form view (opening it), part of the right hand side is cut off such that it no longer looks like equally sized padding.
What's weird is that if I look at the form in layout view, the form is not cut off. And if I then open the form FROM Layout view, the form is also not cut off. But if I open the form in any other way (from a button, vba, right click open from navigator etc.), it is being cut off every time.
Does anybody know why this might be happening and how I might fix it?
Form being cut off
Form not cut off in layout view
Form not cut off when opened FROM layout view
I found this issue occurs when working in access with a higher display resolution than 1920x1080. 3440x1440 in my case.
The only solutions I have found is what you described by opening the form in layout view then switching to form view then save the form.
Only other option is changing display resolution.
I'd like to share a "work around" on this same subject, hopefully it may help in certain cases where the issue is NOT due to Form Sizing through VBA code, which is determined to be the cause inadvertently.
My scenario:
Popup forms, set to auto center, auto resize, fit to screen = truncated, or overcropped form (and DESPITE my own VBA sizing code, which doesn't seemingly "take" or correct the issue).
I usually/often have the scrollbars property set to "neither", so I tried setting "both" on, and the popup form is no longer truncated. I then tried with ONLY the "Horizonal" bar set to on, and it still worked correctly. I then turned both BACK OFF and the form still sized correctly. I saved the form and it appears to have retained the "sizing" properly going forward.
It's as if when you turn these options to neither, the space normally occupied by those scrollbars is "taken off" the borders of the form "again" so maybe toggling that property to both/vertical only/horizontal only/neither "resets" and corrects it. Just a guess.
Hope this helps, spread the word of this little "work around."
O.W. Khan
Related
I have this site here (using bootstrap 4.1.2):
https://secure2.convio.net/cco/site/SPageServer/?pagename=RFL_NW_QC_Impact
And for some reason the dropdown button in the top right works on mobile, and on most of desktop but screen sizes between 786px to 991px won't work, any smaller or larger and it works perfectly.
Someone else created this page so I'm trying to help fix the issue but I can't pinpoint what's causing it. Doesn't seem like a situation where z-index would need to be used because it can still be clicked it just doesn't expand.
I checked the console and fixed the errors that came up but that still didn't solve the issue. Normally it's on mobile where I have this problem because something is overlapping the button but it doesn't seem to be the problem this time.
any help would be greatly appreciated.
thanks!
Opening/closing the menu is done by two custom functions contained in a <script> tag placed in <head>, on lines 187 and 195, respectively.
Each of them has the entire body of code wrapped in a condition:
if ($(document).width() <= 768) {
...
}
Change both conditions to if ($(document).width() <= 992).
You also have another, potentially bigger problem:
On line 391, you have …</script>, ending the current script abruptly, which is a sign that code was copy/pasted from a browser source code, without properly viewing the entire source code (when viewing large chunks of code, Chrome shows the first n lines and hides the rest under …, which acts as a link to the rest of the code). I'm surprised your console isn't bleeding heavily.
The proper way to retrieve the source of a particular tag is to right-click on it in dev-tools and select "Edit as html". In the opening editor window, you can Ctrl+A, Ctrl+C to copy the entire contents of that tag.
After any handful of events, these random square boxes with dashed lines appear all over my application's forms. I can't figure out why or how they are being generated. Is there some type of workaround for this issue? It doesn't seem code or design related.
It's a known bug in Access 2010 (and 2007?). You have a button on your form that has an image on it, with the size of the dashed rectangle.
The rectangle appears once the button has had the focus, and it won't go away. :(
Your database was probably migrated from Access 2003?
See here or here or here.
A possible solution from the second link:
Set the 'Picture Property Storage Format' property in Options\Current Database to 'Preserve source image format'. Try setting that property as well as resetting the picture property in the control.
I must try this sometimes, too. It's rather annoying.
Or if you are not really attached to the image, changing the button to text-only will be the easiest fix.
I am trying to create a input box somewhere on the screen in chrome, not attached to extension button like a normal popup,
it also needs to be running all the time so the user doesnt need to click the extension button to open it, for example so they do not have to come out of fullscreen.
What i have so far since im not great at html or java just a simple form
What i have: http://i.imgur.com/xCY1a41.png
What i want: http://i.imgur.com/cJH8bD4.png
I would also like to control the position of the form but from what i have above doesnt seem as if i will be able,
Sorry if its a bit vague but anything helps!
What you want to do can't be done in Chrome. This is by design. If web content could display itself outside the boundaries of the browser tab's content area, then users might be confused who was presenting it. Confusion is just the beginning of that problem: if web/extension content could masquerade as a system or browser-level alert, then that content could trick the user into doing something dangerous.
If you need a presence outside of a browser tab, your options are a native app or Chrome App.
If you want the input box to be displayed on the page you could use content script - then it would appear as you presented.
Im having an intermittent problem where forms open in view mode but minimised, looking like a small inch-sized box with the 'X' close button visible.
It normally seems to happen when Ive made a change to the form or code in the forms module, but happens randomly when being used in view mode.
I can only get round it by either re-importing a backup of the form or making the form border sizeable, either way it's not too professional.
Any ideas how I can solve this one?
Docmd.Restore seems to work on the form load event
This may be the dumbest question ever but our customer really wants this. I am asking this silly question just to be sure that it cannot be done.
We have a popup window which has opened by window.showModalDialog (img 1)
In this window there is a custom autocomplete control which displays an html table. The problem is autocomplete table is wider than the modal dialog. So user is unable to see the contents of this table. (img 2)
Then we made initial size of the modal dialog wider enough to see table contents but customer did not want the initial empty area and did not want the content to be wider also. (img 3)
The customer wants to see the thing as in img 4 which i could only made by paint.
Is it possible to display overflowed html content outside the browser. At least for the ones which has opened by window.showModalDialog.
Note: This is about a 10 years old project and it is totally based on window.open and window.showModailDialog. So using a custom jquery dialog or something similar is not an option.
Within your client's constraints, your task is not possible.
What you could do instead is popup another modal window that shows the contents of the dropdown. That way, you can get a differently sized viewport than what the first modal window offers. Also, if you open the new one as a child, you could even pass messages between the 2 windows.
Of course this will be a very rudimentary stone-age solution! You may also come across a lot of browser limitations/quirks.