Nov 02 2021 03:13 AM
Nov 02 2021 03:13 AM
I have created one function in Microsoft access and I am trying to run that function using autoexec macro, but I am getting the error as shown below even if I am using the same function name that I have created.
Idk what is the issue with this
Any help would be appreciated.
Nov 02 2021 05:01 AM
Nov 02 2021 05:30 AM
yes, it is a function not a Sub
and I am using standard module not a form module
And the function I am using is :
Dim strPathFile As String, strFile As String, strPath As String
Dim strTable As String
Dim blnHasFieldNames As Boolean
' Change this next line to True if the first row in EXCEL worksheet
' has field names
blnHasFieldNames = False
' Replace C:\Documents\ with the real path to the folder that
' contains the EXCEL files
strPath = "C:\Users"
' Replace tablename with the real name of the table into which
' the data are to be imported
strTable = "data"
strFile = Dir(strPath & "*.xlsx")
Do While Len(strFile) > 0
strPathFile = strPath & strFile
DoCmd.TransferSpreadsheet acImport, acSpreadsheetTypeExcel9, _
strTable, strPathFile, blnHasFieldNames, ""
' Uncomment out the next code step if you want to delete the
DoCmd.DeleteObject Table, "data"
' EXCEL file after it's been imported
' Kill strPathFile
strFile = Dir()
Nov 03 2021 03:32 AM - edited Nov 03 2021 03:33 AM
You didn't tell how you refer to the function in the macro. Maybe you just didn't add the parenthesis, i.e. in the Function Name property of the RunCode action you should have: FetchData()
Nov 03 2021 03:55 AM - edited Nov 03 2021 03:55 AM
Another common reason for the message are security restrictions. Do you perhaps see yellow warning triangles on actions in the macro editor?
Is the database in a "trusted folder" or have you disabled macro security?
Nov 15 2021 08:04 PM
Dec 02 2021 05:52 AM
Dec 02 2021 09:01 AM - edited Dec 02 2021 09:05 AM
For info, functions are always public unless specifically labelled as Private. The quote below is from the article that you linked
Also, the OP has already confirmed the function is Public
Dec 02 2021 09:13 AM
I don't remember if we have already advised him to do a check inside VBA in order to see if the function is reachable at all:
1. Open the Immediate Window of VBA by pressing <Ctrl>+G anywhere in Access.
2. In the Immediate Window type the name of the function , i.e.
and press <Enter> in this line
If the function executes, it is really public and should be reachable also for macros.
Dec 02 2021 10:44 AM
Dec 02 2021 11:14 AM
After intentionally naming the Function and Module the same exact name and running the Autoexec macro I was able to force the same error message as OP.
Assuming the OP has the same issue, it should throw Error 2425.