Untraceable Message Box

[Darrell]

I am getting a message box with obviously custom text
popping up. I recall several months ago creating this
box, but don't remember exactly why. I have scoured all
the code, and can find no MsgBox definition containing
the displayed message OR any event code corresponding to
the generation of the message box. Does anyone know where
I should look to locate where this box is being generated?

Thanks for any help you can provide...

 

[Dirk Goldgar]

I am getting a message box with obviously custom text
popping up. I recall several months ago creating this
box, but don't remember exactly why. I have scoured all
the code, and can find no MsgBox definition containing
the displayed message OR any event code corresponding to
the generation of the message box. Does anyone know where
I should look to locate where this box is being generated?

Thanks for any help you can provide...

A macro? An event property set to a function expression like

=MsgBox("Your funky message")

?

 

[Darrell]

Thank you for the suggestion, Dirk. I just checked the
only macro in the database, which merely opens an
unrelated form, and no errant commands there. If anything
else occurs to you, let me know.

Does corruption ever act this way? Every other part of
the database seems to be working fine, and this message
box is consistently triggered under exactly the same
circumstance, and escaping from the form works smoothly
ans seems to leave no adverse effects. Just wondering if
it is still executing code that I at one point had in the
code but have since deleted.

 

[PC Datasheet]

The clue would be WHEN does it popup. What occurs right before it pops up?
Does it popup ONLY when a certain form opens or closes?

 

[Dirk Goldgar]

Thank you for the suggestion, Dirk. I just checked the
only macro in the database, which merely opens an
unrelated form, and no errant commands there. If anything
else occurs to you, let me know.

Does corruption ever act this way? Every other part of
the database seems to be working fine, and this message
box is consistently triggered under exactly the same
circumstance, and escaping from the form works smoothly
ans seems to leave no adverse effects. Just wondering if
it is still executing code that I at one point had in the
code but have since deleted.

It does sometimes happen that corruption in the database's VB project
allows old, supposedly deleted code to execute. If you think that may
be the case, try decompiling your database (after making a backup, of
course). To decompile, execute a command line along the lines of

msaccess /decompile "C:\Path To\YourDB.mdb"

You may or may not need to specify the path to the folder containing
msaccess.exe.

I still think it's most likely that you're just overlooking the spot
where this message is being displayed. Does it happen only on a
particular form? Does it only happen when you take a particular action?
If decompiling doesn't fix it, give some details and maybe we can track
it down.

 

[Darrell]

I found it... It's in the validation text for the table.
Now I feel a little sheepish since I didn't remember what
I myself did. At least I now know another place where a
message box gets generated--violation of a validation
rule. Thank you all for your time.

Darrell

 

[Darrell]

You're right. I found it... It's in the validation text
for the table. Now I feel a little sheepish since I
didn't remember what I myself did. At least I now know
another place where a message box gets generated--
violation of a validation rule; AND, I know how to
decompile a database. Thank you muchly, Dirk, for your
time.

Darrell