We use a lot of MS Access 2016 reports at our office. For one particular user, they are all now returning #NAME for calculated fields, despite those same reports and fields working for everybody else. This includes other users on the exact same version of Access.
It's been hard to search for info on because most #NAME issues are problems with the report construction. But the reports are all fine in this case, presumably. Are there some program-level Access setting(s) that could cause this issue?
We've tried restarting the machine, as well as running Access as an administrator. Other than these calculated fields, Access appears to be working for the user just fine. We have not yet resorted to re-installing MS Office.
Related
i have a problem with ms access, this the detail of my problem .
I have accdb 2010 file, and then i am tried to make this database online, so i tried split database.
The file_be, i am tried connect to sharepoint, and its success
The file_fe, i am delete the existing table, and get external data from sharepoint, and its success too
I am tried the application, its success, database on the sharepoint was update too, until this, i have no problem, but the problem is
I was copied File_fe to another computer, office 2010, and office 2013, and then when i am running the app, the application directly force close without information or warning, i have tried on 4 pc, and the problem was same, can you help me guys for my problem ?
i am tried many file, and the problem was same
this the link of samplehttps://drive.google.com/file/d/19821F6ID2jxrBqQRfb9hVhueGXeCfGDb/view?usp=sharing
I'm updating a 2006 program written in VB6. It has a large database created with Access 1997 with which the program works fine, but Access 2007 would not allow me to modify the database unless I converted it from .mdb to .accdb.
I did so and in Design mode, changed the DatabaseName to the .accdb extension, left RecordsetType as Dynaset, but when I click on RecordSource, I get an "unrecognized database format" message.
I've researched everything I could find on the web. Someone said to switch from DAO to MS Office Access database engine (12.0) which I did. Someone else suggested using Access (2007) to compact and repair it, which I did.
In Resources, I see *MS ActiveX Data Objects 2.5 library and MS Data Environment Instance 1.0 (SP4). I don't know what they are for offhand, not having looked at this software in a dozen+ years.
If I run it without specifying a RecordSource in Properties, when it gets to the line:
Set rs_BidTable = db_BidBase.OpenRecordset("Table1") (where Table1 is a table in the database)
it gives a "Type mismatch" error message. None of the code changed after the update other than changing the database name in the code.
I could give more detail about what I have in the code, but since it's bombing in Design mode, I'm don't think the code is relevant (is it?).
I have other programs with databases updated to Access 2007 and never had this kind of problem.
Using Access 2013, Sharepoint 2010 OnPremise
I have an Access database that uses Sharepoint 2010 for a back end using Linked Tables.
A few months ago there was a request to have a field contain multiple values, and I stupidly implemented that change, not fully understanding all the issues behind that. Initial research lead to it being "ok" for Sharepoint Lists.
Due to the company architecture, this application needs to be accessible on a Kiosk machine that doesn't have access to the Sharepoint site, but still is connected to the internet.
If the computer runs the application while connected to the internet it will hangup/stall when opening because it's trying to resolve the connection of the linked tables or trying authenticate.
But if the computer runs the application while not connected to the internet it will operate as it should in an offline mode. All data is accessible.
Since we can't/don't want to disable the internet of the Kiosk machine the solution was to convert all the Linked Tables to local tables and issue it to the machine that way.
But now a few months later when trying to make the offline mode application we get the following error:
You cannot enter that value because it duplicates an existing value in the multi-valued lookup or attachment field
I think it has to do with that multivalue field, which has turned into a huge headache, but can't be undone for at least a couple more months.
The Offline mode functionality was created long before the multivalue change, unfortunately that part of the application wasn't tested against this changed field.
So I need to know if there's a way I can convert the table, or if there's another way to Force Access 2013 into an offline mode.
Thanks,
Dennis
I have a Microsoft Access 2010 form where the value of a field is determined by a DLookup using a value in a combobox. Here's the control source for the misbehaving text box:
=DLookUp("companyname","dbo_company","companyid = '" & [Companyid] & "'") where [Companyid] is the combobox in the form.
The database itself is stored in MSSQL. When loading a record the text box with the DLookup remains empty until I click on the text box to force it to update. There doesn't appear to be any problem accessing the database, as other fields in the form are being filled fine (including the combobox with the companyid).
Strangely, if I take this Access project and open it on another computer, the text box with the DLookup will load and display the information immediately upon loading a record. This would seem to indicate a configuration issue specific to my computer, but I don't see where such a configuration option would be. Both computers I'm running this on are using Access 2010. There is no code in the "events" handlers, and I'm running the exact same file on both computers (opening over Windows file share). I've already tried doing a "compact and repair", but that didn't change anything.
This also happens when selecting a value in the combobox - the text box will remain empty on one computer, but will update with the DLookup on another computer.
Why would a DLookup run immediately on one computer, but wait until "GotFocus" on another computer?
Well, it looks like this is a bug within Access itself. The issue appears to be some kind of interaction between the Windows Update service and MS Access. When updates get published on patch Tuesday, it causes the Access engine to go wonky. The short-term fix is to restart the computer. You can read more about this in
this lengthy thread on the MSDN forums
The long-term fix is to apply KB2899528 (Access 2010) or KB2956176 (Access 2013). However, note that KB2965300 will overwrite and reintroduce the issue fixed by KB'528 for Access 2010. KB'300 is automatically applied by Windows Update, and now I can't seem to reapply KB'528, so I may be stuck with restarting the server every month.
I'm running reports in MS Access 2003 which query against our SQL Server 2008 database. Unfortunately when adding new vies to the report form MS Access has begun crashing as soon as I try to view them in anything other than design view.
The program is not throwing out any error messages and the individual views cannot be displayed outside of the report form.
I have converted all of the views to tables as a rather sloppy hack to get these reports up and running. Although this works I'd really like to try and gain a bit more insight into why Access is willing to display some SQL Server views and not others. Note this is not an issue with 2003 I believe because the same behavior is observed in MS Access 2010.
Has anyone run into anything similar?
Any Ideas what may be causing this?
I'd like to avoid having to use my convoluted table conversion method in the future.