Undefined function 'BuildCustomerName' in expression

  • Thread starter Thread starter LostandConfused
  • Start date Start date
L

LostandConfused

Guest
Hello first time poster :)

My boss recently moved a DB from one server location to another and now it is no longer working properly. Please bare with me, I am not very knowledgable of Access and am primarily an oopl coder. I am using Access 97 in an XP.

The database is comprised of 6 files: Service_Request.mde/mdb, Common_Code.mda/mdb/mde, and default.mde. Service_Request.mde/mdb both reference Common_Code.mde and default.mde.

Service_Request has a login screen when you first start it up caused (I assume) by a macro that makes the call: login("frm_requestlist"). A prompt appears where i can enter a user name and login but when I click ok it crashes about 1 minute later with the 'Undefined function 'BuildCustomerName' in expression' error. I can bypass the login with the Shift+F11 shortcut but all of the forms crash when I double click them.

The function 'BuildCustomerName' is located in Common_Code in the module 'Library'. However, I looked through the code in Service_Request and Common_Code and except for its definition, I cannot find a call to it anywhere. Service_Request does make calls to a few other functions in Common_Code, but I am unable to tell if they are working or not.

I have checked the references for Service_Request with a reference wizard and as far as I can tell they seem correct. It references both Common_Code and default in their current locations on the server. However, even if they were incorrect I cant figure out how to change them with my current resources.

Any help in this matter would be greatly appreciated as would tips on how to step code cause I havent been able to figure that out either.

Thank you
 
Last edited:
To LostandConfused:
You might take a look at the links in your tables thats is if the tables are
linked to a backend database file and check that the pathing is correct.
Also take a look at all macro's and and check on the pathing, includes the modules, forms, and reports also. And under Tools - Startup check the pathing there also. And if you decide to do a repair make sure you copy the
original to another directory before updating.
FYI: Need More Management with IQ's of 2 in this world, Eh!
Also notice it's not Management thats trying to resolve the issue,
after the fact. Love it, I understand why your LostandConfused.
Flixx
 

Users who are viewing this thread

Back
Top Bottom