I have a weird issue regarding a text box within a subform that is within the form i am working on. Usually, I do not get this error when I would normally close out of the form via the Close button that was created on it. If I was to close the form via the tab when I'm doing edits, it causes the error and using the Close button stops it when I reopen it. I have no idea how to fix this so closing it through the tab would also not cause this issue.
If the close button works properly and closing the tab does not, then the close button does more than just close the form. Look at the OnClick code for the close button and transfer the appropriate part of it to the OnClose event of your form.
Most likely it is just something like Me.Dirty = False that writes any unsaved edits to the record but there may be more to it.
Related
I had a button click event in my access form which has
DoCmd.OpenForm "frmStudentsAll", acNormal, , , , acDialog
Clicking this button opened the frmStudentAll in dialog view but all of a sudden today clicking this button did not open the form. I thought Access was crashing everytime I clicked this button but I can still edit the VBA but I cannot press any of the buttons in GUI. My thought is that the acDialog is opening a really small form somewhere that I cannot see and I cannot press anything without closing it. I am having to close Access using task manager.
DoCmd.OpenForm "frmStudentsAll", acNormal
Opening the form in just normal view works fine but this is not really what I want. I did not do any new Access updates recently. Not sure why this is happening.
The problem is that the form does open, but is positioned off-screen.
This is a common issue when you have a multi-monitor setup or have different users with different resolutions using the database.
By default, Access stores the location of the form relative to the database window. If a specific user has two screens, or a very large screen, he can easily position it where others can't reach it. And even a single user can position it where he himself can't see it, by first positioning it on the first screen while Access is open on the second screen, and then opening Access on the first screen.
To avoid it, set Auto Center to Yes in the property pane for the form. That makes sure the form is always centered with respect to the Access application window, so always is on-screen as long as Access is on-screen.
Alternatively, when you're locked out of the database because of this issue so can't adjust the form, you can use Forms!frmStudentsAll.Move 0,0 in the VBA Immediate window to reposition it. That way, you don't have to close the database when this occurs.
Not sure if this will help or not but, I'll throw it out there anyways. I had a similar problem when I had two monitors set up. Then lost one. There was one program that I would use all the time but, all of the sudden it wouldn't work. Took a while for it to kick in. That program was opening on the second screen that was no longer there. Just a shot in the dark... Good luck!
I faced with a strange problem. I write ASP.NET web application.
I have form tag on the aspx page and submit in the form. When I click on the submit form's data are posted. It is ok. But if I close the page right after submit and then re-open it with Main Menu -> Recent Tabs (I use Google Chrome) the form's submit fires once again and data are posted too. I would like to avoid this behavior because repeated posting data to server is unwelcome and unexpected. It happens after select Recent Tabs only (when I prress Ctrl+Shift+T it does not happen) How could I prevent it? Thanks in advance
Check if it's a PostBack. If it is a PostBack then return.
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
I have a click_event handler on a Tab page but when I click on it, nothing occurs and with debug I can see it is never triggered.
Is this a bug ?
When code starts misbehaving, it is often worth trying decompile.
http://www.granite.ab.ca/access/decompile.htm
Say if I am on page 1 , I enter my form data and go to page 2 , But wait I forgot something and I need to go back. FireFox and Safari ask me if I want to resend my form data.
But IE being IE it just goes back and does not show the page.
Is there away around this when I click back it keeps the data and the page appears.
Sorry I cannot give a link but the process for u to go through on my site to get to this part would take you a while.
My suspicion is that your talking about a wizard form. Where each part of the form is a page and you can go backwards and forwards through the pages.
the back button has always caused problems for developers on the web and this is probably the most annoying.
You can stop the IE back button issue by redirecting on the server to the next page when you receive a form post rather than just delivering the form back to the browser. Doing this means that the browser considers each page to have been a get and stops asking you if you want to resubmit the form.
to do this simply make each form post to itself and then return a redirect to the next page of the wizard. I'd give examples but I'm not sure what language you are using on the server.
the other alternative is to use javascript to create a wizard from your form see this jQuery wizard form demo.
create a new back button besides the submit button and when a user clicks on either one you call a javascript function which modifies the form action either to the next page or the previous page.