Microsoft can't find the function

Question

I'm trying to build a Relink table function, I've used several different VBA functions found on the net I understand the reason why I can't get some those to run but what really makes me pull my hair out is when access throws an error at you saying it can't find the function when it is clearly there, I can see it. So, I'm running a macro Autoexec using RunCodeFunction Name Reconnect I have tried this macro with a function name of Reconnect() and even Reconnect using both (True and False) just to see. And me, well I just sliding into a mess on the floor 

I'm using Access 365 to learn, test and build the application 

The major problem I have is the Access 2010 I'm using at my place of work (The IT Wizards looking after our system) will not allow any reference tools within Visual basic to reference anything, hence the reason why I've tried and tested so many different internet provided code and just to make matters worse the PC's my Access app will be running on will only be using Access Runtime,

Is this project of mine possible with the tools I have? 

I know I'm really asking two question here but can anyone shed some light, If the latter can't be done I'll just have to persuade my manager purchase  and install Office

Hope someone can help

Answer 1

In addition to Daniel's suggestions, I expect you might have named the module the same as the function. This is one of the reasons I begin all module names with something unique that won't be the name of anything else in my application.

Answer 2

dhookom

doh! I'm such a beginner can you believe, you rack your brains forever, looking here, there and everywhere and it nearly always is the simplest of things big thanks

Answer 3

With regards to your function:

Did you place it in a standard module (not an object module, not a class module)? 

Did you declare it as Public?

Did you declare it as a Function, not a Sub?

Does your code compile?

Why not supply us with a sample database to review?

As for the rest, you will face a serious problem at one point trying to develop using Office 365 and then bringing it to your office running 2010.  You always need to do all your development using the oldest version that will be used to run your database.  In your case, you should do all your development in 2010.

I must say i don't understand what your IT department can do to references.  They can block the most fundamental built-in references from working, otherwise Access wouldn't work at all.  Beyond which the are numerous times that require no special references to run.