Forum Widgets
Latest Discussions
Block users from exporting queries and tables
First off apologies very new to access and databases in general, but I am having an issue where users can just grab my queries/tables out of my access database with excel. I'd like to know how I can prevent it. Current things I have tried. Shift bypass disabled Forced into runtime via script Split the database and encrypted the back end Saved as an accde Hidden the tables/queries No matter what else I try a user can just open excel click get data and has a free pass to copy everything. Is there anyway to stop them from pulling the tables/queries out?
Access keeps giving syntax error
Hello, I wanted to classify test results in different groups and used this formula for a calculated field in a table: IIf([Testscore1c1]>28,'Plus',IIf([Testscore1c1]>15,'I',IIf([Testscore1c1]>6,'II',IIf([Testscore1c1]>2,5,'III','IV')))) This worked (although I started with " " and had to change them to ' ' for my Dutch Access365 to accept it. The problem is that I copied this formula and wanted to use it in a different field (only changed [Testscore1c1] to [Testscore1cR] which is in the table as well. But the same formula is now giving me endless syntax errors without telling me what is wrong. I've tried everything I could think of and have spent hours searching for answers online already. Could you help me?
Query error 3141
Yesterday I started my Microsoft 365 free trial. I created a database and made a query, when i tried to save the query i got error 3141"The SELECT statement includes a reserved word or an argument name that is misspelled or missing, or the punctuation is incorrect" but the spelling was correct. So i tried a new database and got the same error again when saving a query. This error happens with multiple different types of queries across multiple databases and when i download a database with a query already in it and copy the code from the already made query into a new query it still gives the error 3141 even though it works in an already made query. I assume this has something to do with my Microsoft Access. this is the query i made: SELECT * FROM ttblTraits;
Linking Access to Excel does not work
I have created a simple Access that is connected to a linked table to an Excel file as a data source. I can run the Access without any problems. It accesses the data and everything is fine. But when my colleague wants to run the Access, she gets the following error message "Microsoft Access “C:\Users\User\ [Source Path] .xlsx” is not a valid path. Please ensure that the path is entered correctly and that you are connected to the server where the file is located." We use OneDrive/SharePoint in our company and the colleague has access to the folder where the Excel and Access files are located. But it doesn't work. I think it's the path, as it seems to be local. But I don't understand why. This Access in turn serves as a source for another Excel (the target file). There it has a similar error message: ‘’Microsoft Excel [DataFormat.Error] “ [File Name] .accdb” is not a valid path. Please ensure that the path is entered correctly and that you are connected to the server where the file is located." I can open and run both the Access and the target Excel without any problems. Thanks a lot in advance. I appreciate your help a lot.The New Access Features in 2025
Hi, Yesterday, I posted two videos on my YouTube channel. They are a short version of the presentation given by the Microsoft Access team at my recent Access DevCon conference. They show a lot of new features they are working on and that are planned for the rest of the year: Breaking Access News - Signing/Monaco/SCC/Charts Breaking Access News - Zooming and Extending Form/Report Size Limits Here is my article with some more explanation: https://www.accessforever.org/post/the-new-access-features-in-2025 Servus Karl **************** Access Forever News DevCon Access-Entwickler-Konferenz AEK
Access changing lettercase - redux
This has probably been beaten to death, but I'm fuming, so here goes. I want Microsoft to DO SOMETHING to help. Access has the highly annoying habit of changing lettercase on identifiers, seemingly at random. This is a real pain when using add-ins like MSAccessVCS, which makes it possible to use git for source code control. Here' what I've deduced is happening: There exists a dictionary/symbol-table containing every identifier used in a project. The symbol table contains ALL identifiers, including those defined by MSAccess, referenced libraries, and your code. Searching that table is case-insensitive, but it stores the canonical version of the identifier with case preserved. Normally, when you type an identifier that already exists in the table, the VBA editor "corrects" the lettercase of your entry to match the table's entry. The extremely annoying part is that sometimes that last step works in reverse. You type an existing identifier, but with a different lettercase. Instead of correcting what you typed to match the table, it instead updates the table with the version you typed, and decides that's the way future and existing identifiers should be spelled. Here's a recent example. I tried to create a class module constructor (Class_Initialize) but typed it "class_initialize" implicitly expecting that the VBA editor would "fix" it. Instead, it updated the symbol table and set the canonical lettercase to the all-lowercase version... and then proceeded to change the lettercase on the Class_Initialize() method in all my class modules. It has now decided the canonical lettercase is "class_initialize" and that's what it "corrects" to from now on. Of course, when I did the next MSAccessVCS export, git showed a bunch of unwanted (but cosmetic) changes. This pollutes the changeset and makes source control more difficult. THIS. IS. A. BUG. My workaround is, when starting a checkin, I go through the list of changes and group all such changes into one commit called "VBA Artifacts". But come on, this shouldn't be necessary. At least let us know WHY this happens, and give us some control of the process. A way to specify/correct the canonical casing would help.
Select Query values not showing in report - MS Access
I'm probably missing something simple, but.. I have a Table that has 4 field (plus key), Company ID, Join Date, Quit Date, Notes. This tracks agency membership I made a select query, with 2 IIF statements, and 2 conversions. My Datasheet view shows correctly, but when i put the fields on a report, YRSCALC is empty, and doesn't sum, which affects Grand Total. I have tried every type of formatting i can think of.. Select Query: SELECT tblJOINQUIT.[Company ID#], tblJOINQUIT.[Join Date], tblJOINQUIT.[Quit Date], tblJOINQUIT.Notes, Sum(IIf([Quit Date] Is Null,"0.00",DateDiff("m",[Join Date],[Quit Date]))) AS NumOfMonthsCalc, Sum(IIf([Quit Date] Is Not Null,"0.00",DateDiff("m",[Join Date],Now()))) AS NumOfMonthsCurr, [NumOfMonthsCalc]/12 AS YRSCALC, [NumOfMonthsCurr]/12 AS YRSCURR FROM tblJOINQUIT GROUP BY tblJOINQUIT.[Company ID#], tblJOINQUIT.[Join Date], tblJOINQUIT.[Quit Date], tblJOINQUIT.Notes; Report View: Help??
