Module compiles, exicutes okay but can't create accde

[GraeagleBill]

I have a simple "Public Function" that compiles without errors and runs correctly without errors. (The Run Code macro is AutoExec)





I "Run to Cursor" in debug with a test sub and all works as expected.

Public Sub TestMedCheck()
Call MedCheck(0)
End Sub

If I try to "Open" the accdb or create a accde, I get an error Access can't find a macro. Same thing with "Compress & Repair"

[isladogs]

Make sure you have Option Explicit listed at the top of each code module to ensure all variables are declared.
Now run Debug...Compile again and fix any errors.
Once that is done, you should be able to create an ACCDE

[GraeagleBill]

ALL my general and form modules head with:

Option Compare Database
Option Explicit

Why I get this with make accde and compress and repair is still a mystery to me.

[Micron]

It's probably some other function that you've forgotten about. Maybe one called by some query or control?

[GraeagleBill]

That's what I thought at first, but I've scoured the code and as yet haven't found it. I'll take a nap and then look again

[Micron]

Could always submit the db for additional inspection, but enjoy your nap. Maybe you'll come up with some ideas in your dreams.

[Gicu]

Is the module name the same as the public function (MedCheck)? If yes then that is your problem.

Cheers,

[GraeagleBill]

No, I use a type prefix on all my stuff, like Mod, frm, rpt,tbl, Q, etc. So the module name is ModMedCheck while the function name is MedCheck. Same with variables, str, lng, int, var, etc.

[GraeagleBill]

I think I've attached the zipped DB? (It's okay if you run the code, as the only outcome would be for me to receive a text message, just limit such to the continental US.)

[GraeagleBill]

I just got a text
and another

[Micron]

Must have been me. Didn't realize that would occur and have no idea at what point.
I first tried importing all into a new db - no dice.
I tried removing function, closing, decompiling, opening, pasting back in and compiling - no dice.
The only thing that seems to work is calling TestMed instead. At this point I'm stumped because besides all of that I made sure it was a function call and that it was public in a standard module. I also tried calling my own function with text and long variables and that worked.
Also created a new macro and tried calling MedCheck - no dice. Changed function name to Med and that worked in my new macro.
Changed your function name to Med and it works - Med(0)
It doesn't like the name MedCheck!

[Micron]

VERY BIZARRE! It will work as MedChk(0) and MedChek(0) but not MedCheck(0). It's as if it's rejecting Check as a reserved word.
That's GOT to be a bug.

[GraeagleBill]

MedChk gets the job done. I've never run into a goofy one such as this caper has proven to be. I know solving it wasn't without some effort on your part, so I thank you!

[Micron]

You're welcome. It's not one I'm likely to forget for a while.
With a bit more testing I figure it's not the length of the name by any means. MedChekk was OK too, and when I reverted it back to MedCheck all of a sudden the function name was presented when I began to type Med in the macro field, which it never did before. I thought "Here we go, it's going to work." Still failed. Tell Bill next time you see him.

[GraeagleBill]

That's GOT to be a bug

Sure seems that way to me.