Ms Access pop-up forms off screen - ms-access

I am currently working in MS access 2013, and having an issue with some forms that worked previously. I have gone back and edited them to have different functionality. I need the forms to be pop ups. Now, they work perfectly when they aren't pop-ups, but as soon as I change the forms to pop-ups the forms pop up off screen. I have no clue how to fix this.
Now the first thing I did was start from an old verison, and I was just going to remake the form; however, as soon as I change ONE thing from those old forms the form starts popping up off screen again.
Has anyone had this issue or know how to resolve it?

If you have two monitors or if your application is created in a secondary monitor and used in a single monitor machine, this behavior is expected. As EvDev mentioned. Set the "auto center" = Yes and edit your application in the default monitor.

Set the Auto Center property of the form to True.

Related

Frame size issue in metaphone3 cluster and edit

I am using OpenRefine to clean text from a CSV file. I've been working on the same project for several weeks, and it was working fine until this week.
I am trying to use the 'Cluster and Edit' function from the 'Edit cells' menu. When I use the 'fingerprint' and 'ngram fingerprint' keying function, the frame that opens up inside the browser window is sized appropriately, and I have access to all the buttons and selection menus. However, when I try to use the 'metaphone3' keying function, the frame that opens up is way wider than the browser window, the sliding selection boxes that usually appear in the right side of the frame are not visible, and the buttons across the bottom of the frame ('Select All', 'Unselect All', etc.) are not available. I'd really like to be able to use this keying function option again. Does anyone know what's going on, or how I might be able to fix it.
I am using the OpenRefine 3.3 beta, although a similar issue was happening earlier this week with all keying function options in 3.2 (all were working fine in 3.2 as recently as Friday, 10/25/2019). I am using Firefox, although the same issue happens in Internet Explorer. The system OS is Windows 10 Enterprise.
Thanks in advance!

Microsoft Access form opens minimised after its been changed

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

Auto suggest with Rendering issue

I have an issue in our currently running .net application. we are using autocomplete extender control associated with city textbox for city selection. Due to slow internet connection, when user uses this application with partially rendered, it is not suggesting for entered city (highlighted in red).
I have used Page_Init event for first disable the textbox, than enable it on Page_Load, but it's not working (to prevent user for enter text when the page is not loaded completely).
Is there any solution to overcome this problem?
After loaded successfully,
So you want to disable the textboxes until the page has loaded? I am not sure if it will work like you want but have you considered using jQuery to disable the textbox? For example here, here, here

Disable back space key for browser based AS3 application

this is insanely annoying problem:
AS3 full screen application based on ADOBE FLEX 4, text field. User types something in text field, and then starts clicking backspace many many times to remove what he just wrote, and for some reason, instead of removing characters from text field it tells browser to GO BACK and user navigates away. Why?! Please, please help, this is so terrible. My users are losing important unsaved this is data while using my application!
i am using safari browser
PLEASE HELP.
Wow, this is terrible, I am so irritated, it happens every single time
It is possible that the focus is lost from your text field when hitting the backspace multiple times (check if you are firing some events on the text field that may cause this), which causes the main window to take focus and trigger 'Back' on the browser.
The root of the problem is that the browser carries out keyboard shortcuts REGARDLESS of the flash app having the focus or not. From what I heard this problem does not exist on Safari's for Mac, only Safari for Windows.
I would check to see what browser you are in and then create a popup saying you this app does NOT work on Safari browser ON windows.
Scratching head*
Well maybe if HAD to solve this, I would use the ExternalInterface to interact with Safari or javascript to PREVENT the history back button from getting applied. So it won't go back to an old page. That is what I would look into.

ASP.NET 4 UpdatePanel breaking change

I am porting an ASP.NET application from 3.5SP1 to 4.0. The application works perfectly in 3.5SP1. In 4.0, I am seeing a difference in UpdatePanel behavior.
We have a simple user control with a testbox, a button, and some text. The user control lives inside an UpdatePanel with UpdateMode="Conditional" and ChildAsTriggers="true".
Users type into the textbox and click the button. We do a search. If we find something, content elsewhere on the page is updated - this works great. If we don't find it, we change the text in the user control. That change never appears.
So I know the button and logic is working. The user control does not own the UpdatePanel it lives in, and it would be nice if it didn't have to. But even though the button is raising an event back to the server, the update panel content is not updating.
Has anyone seen this?
My problem turned out to be 4.0's new client-ID mechanism. Check out the new features here.
4.0 defaults to 'Inherit' while 'autoID' is the 'old' behavior. By adding this to the web.config pages element:
clientIDMode="AutoID"
my problem went away. I'm not wild about forcing backward-compatible behavior but until I can sort thru all the control relationhips this will have to do.