I modified a frm and its associated tbl incorrectly and am now getting the Enter Parameter pop-up for the 6 or 7 fields I altered the names of when I launch the form. There is only very simple VBA attached to the form doing formatting on OnLoad, GotFocus and LostFocus.
My company hasn't loaded the Analyser toolkit into Access 2010 to let me use Documenter and Analyse tools and I don't have Admin rights.
I have been through the queries, table and form to ensure there are no artefacts lingering but to no avail.
Is there a work-around that anyone's discovered?
Thanks
Related
I have an ms Access form that is linked to query.
The query depends on a control on another form to filter the data
I set the view of the form to be Data Sheet View to have the capabilities of filtering and sorting.
The form at start responds to the Requery command correctly.
When filter is applied to the data it keeps responding to the Requery command
When the filter is removed it stops responding to the Requery command. Command is executed normally without any error but displayed data doesn't respond to the change.
I run the underlying query at the same time and it responds well.
When applying any filter again the response returns to normal again
Do any one have a clue about this problem?
I am using Ms Access 2019 64bit (integrated with Office 365 package)
Here is sample database link to clarify the problem. Run frmMain and follow the steps on the right to replicate the problem
DemoDB
For anybody dropping here I had an answer from Microsoft Community as follows (related to shared demo sample):
Change the code for the button Check8 to:
Private Sub Check8_Click()
If Me.frmSubSub.Form.Filter = "" Then
frmSubSub.Form.RecordSource = frmSubSub.Form.RecordSource
Else
frmSubSub.Form.Requery
End If
End Sub
This worked fine for me despite the demo shows there is a bug in MsAccess to deal with this situation.
Link to question on MS Community: Link
Even though I'm new to access, things were progressing well, but I've hit the wall with a few issues. I've inherited a split database with four pieces, a backend version, frontend version and two user versions in accde form. The users wanted some changes, so I needed to add a few forms, modify a few forms, add a table and come up with the queries for the changes. That work is complete and I was able to convert the new frontend accdb version to the user accde versions. Some of the users are able to open the database, but some of the users are getting a Macro Single Step message with the following information;
Macro Name: AutoExec
Action Name: RunCode
Error Number: 3270
There's also a message about the backend location not being a valid path, but of course it is.
I'm wondering what the differences would be between the users who are able to get in and those that aren't. I've added the location to their trusted sites and I've changed their macro settings with no success.
Any thoughts would be appreciated, thanks, Bill
In an application I have two ribbons: a "General" one which is used for all forms, and a reports-specific one for all reports. From a "Reports Manager" style form, a user can select a report and preview it.
When the report opens, it correctly displays the Reports Ribbon. However, when the report is closed, the Reports Manager form is still showing the Reports Ribbon, instead of the general one.
Once this form is closed, the Ribbon changes back to the general one.
Note that users access this application, as an accde, via Terminal Server.
This incorrect behaviour does NOT happen on a local development machine, so I suspect it is due to a TS 'refresh' issue - which I have noticed in a couple of other circumstances.
Is there anyway to 'force' a refresh of the Ribbon when a report is closed, and the Reports Manager form is therefore displayed?
I would consider in your startup code grabbing a handle to the main ribbon (that is not re-displaying). Then in the reports on-close event execute a ribbon invalidate command like this:
MyMainRibbon.Invalidate
So you can “force” a ribbon re-plot. This does suggest you always use a accDE, since with a accDB then any un-handed error will ALSO lose the above global var that holds a reference to the ribbon.
I made Access Form which was working fine in Access 2013 and Access 2007 until I add some new features(I don't remember what) to it.
After adding them, it keeps giving me error "Unrecognize file format" when I try to run it in Access 2007. Meanwhile it runs fine in Access 2013.
I want to ask if there exists some software to convert Access 2013 file to Access 2007? Or is there any way make it compatible to 2003? When I Save As 2003 file it don't because of some added features.
Please help!
You could try using Access' Application.SaveAsText in 2013 and Application.LoadFromText in 2003.
Even if this doesn't work directly, if you have an older version that does work, you could compare the differences between the text files the two versions of Access produce, as SaveAsText produces (for the most part) human readable output; the only unreadable parts are typically images.
I've had this happen to me during development on A2010 and deployment on A2007. The possibilities are explained on this page. It is likely that you added an Empty Cell control to a form that had a VBA module (or added a module to a form with an Empty Cell control). I did this unknowingly by inserting a row into the AutoHeader that is created in forms by the Form Wizard.
Follow the steps at the bottom row of Table 2 to rectify this.
I am working on an Access 2007 application that was created by someone else. It has a strange, intermittent bug in which it prompts the user for query parameters when the main form is opened. The query parameters are clearly not necessary, because the error does not always occur.
The very strange "fix" to this problem is to open and close a particular module before opening the main form. Then the form opens without parameter prompts. However, of course I can't ask end users to open and close modules.
I tried using a macro to open and close the module when the database is opened. That fixes the bug, but leaves the VBA code window open, so that's no good.
Has anyone run into anything like this before? Any suggested solutions, workarounds, debugging tips, etc?
If you use the "Database Documenter" feature and check "yes" to all the options, you will obtain an exhaustive report that should let you trap your problem parameter. Export this report as an .rtf or .pdf document, so it is searchable. Identify a keyword from the dialog prompt, and search on that.
Once you check the query objects using the Documenter, check your VBA code. You'll do this by stepping through code in the IDE. If the main form has subforms, they are opened with (within) the main form. And they load before the main form.
Identify those subforms.
Sprinkle
breakpoints in their code modules
(if you find a Load function, that
is highly relevant).
If the main form has a
code module, do the same there.
Have a look for global variables in the module that needs to be opened and closed or any variable that is referenced in the module belonging to the form.
Access displays the Enter Parameter Value dialog box when you open an object that contains an identifier or expression that Access cannot interpret. You need to determine the source object. Here's a step-by-step guide:
http://office.microsoft.com/en-us/access-help/why-does-access-want-me-to-enter-a-parameter-value-HA010274377.aspx