The expression may not result in the name of a macro, the name of a user-defined function.. error

[robs23]

Hi Guys,



Every error I got during my adventure with Access had more-less clear cause and solution. Every error but this one:

The expression On Load you entered as the event property setting produced the following error:

* The expression may not result in the name of a macro, the name of a user-defined function, or [Event Procedure].
* There may have been an error evaluating the function, event, or macro

It seems to be caused by onLoad/onClose event on one of my forms. This error occurs without any apparent cause and go away with any reasonable cure as well. Very often it helps when I clear the field "On Load" on "Event" tab in form's properties and set it back to "[Event Procedure]". Of course it was "[Event Procedure]" before also, but this seems to do the trick most of the time.

Unfortunately this time it doesn't want to go away. It happens when I try to run .accde file on Windows Server using Access Runtime 2010. I have no idea why, nothing changed in the file and it had been working perfectly well before. At some point it just started to give this weird error.
I already tried to replace the file with the original one, uninstall/install back Access Runtime, importing all to new database file etc. with no success. It runs well on full Access (both full and runtime version 14.0.6029.1000).

When I take the .accdb version of the file, it ends up with error:

execution of this application has stopped due to a run-time error

When I browse other threads about same errors, I'm lead to the conclusion it's about missing reference.. That's kinda weird as it worked perfectly well before..

Can you help me nail this error? How do I check if any reference is missing on the "runtime" maching?

I'm attaching a zipped copy of the file. Please press "SHIFT" to omit start-up options.


Robert

[June7]

You provided a db that won't run. The only form executes code on open that wants to connect to a backend with password control. How can we debug if can't run code?

I do see drive letter pathing in the Start_Up procedure. This might be source of issue. Does every user have the same path mapped for F:\1356\Common ? Suggest you use UNC pathing instead and mapping is irrelevant:

"\\server name\1356\common"

[robs23]

Hi,
I know that. I provided only a server script file that is supposed to update back-end every 5 minutes - back-end itself hasn't been provided as I'd have to remove a lot of data. Besides, if it runs to the stage where it pops up "F:\1356\Common\npdmanager_be.accdb" is not a valid path, it means it runs in your configuration and would work perfectly well if back-end is present. "F:\" is a server disk from the server's point of view (same as e.g. "C:\" is my computer's internal location). This file itself is not distributed to end users, it runs on server and update back-end etc.

Robert

[June7]

If the db is not distributed, why bother making it an accde? The accdb doesn't indicate a missing reference and I have no idea why accde would nor how to determine what the accde thinks is missing. I've never used runtime or executable database. Sorry.

[robs23]

I forgot to answer here. As it turned out no reference was missing. It helped when I've added a proper error handling to each subroutine and function. Stupid error handling, I'm usually to lazy to include it. Thanks.