Normally in the VBA IDE you can select one of your function calls, right click and choose Definition from the pop up to jump to wherever that function is written.. Well, all of a sudden I can't do this in my database - it goes to the object browser and gives me the message stated in the subject of this post - can't jump to 'function name here' because it is in the library 'full path to the current database (on a mapped network drive..)' which is not currently referenced.

Now I know that I can fully reference all of my function calls by placing the module name in front of them but man! That could take a while and I know that something else is wrong which I'd like to find and fix..

I don't know if I've done anything recently to mess up my system - I haven't installed anything recently - though it is a work machine and patches are pushed out all the time..

Anyway, I'm hoping that someone else knows what to do off the top of their heads - I've already spent about an hour and a half googling this stuff after I spent about a half hour looking at old copies of the database and trying it on different systems (the problem existed on a different workstation in every old copy of the database that I opened) but it didn't used to do that..

Maybe it has something to do with the mapped network drive which is DFS and could have possibly moved recently...

Answers

Recently changed naming conventions.. Turned out that this particular function (and several others) were named the same as the data column bound to the form... ie, Field name: RequestTypeID - function: RequestTypeId

So, I reverted back to my old naming convention which includes function or sub reference as well as the return data type.. And I can't wait to write my boss an email about the naming convention changes that I originally fought!

So, I checked other functions in this same project - I was able to jump to some of them!! So I commented out the original function, then created it again - problem persisted. So then I renamed the function - problem gone!

The name of the function is:

RequestTypeID

returning an integer..

I don't know if that means anything to anybody - reserved word or something?

Recently changed naming conventions.. Turned out that this particular function (and several others) were named the same as the data column bound to the form... ie, Field name: RequestTypeID - function: RequestTypeId

So, I reverted back to my old naming convention which includes function or sub reference as well as the return data type.. And I can't wait to write my boss an email about the naming convention changes that I originally fought!