sub intentianally not defined

[markjkubicki]

I have a condition where the module that a sub would have been located in will INTENTIONALLY be deleted (and by default the sub.)
Elsewhere in the project there is a line of code that would call the sub - if it still existed (It's OK when it does not, that part of the plan...)

Thought this below code would get me around an error call when it no longer does (and i thought it had), but as a clean-up... this seems to not be the case(?) ()maybe it never was?): I do get the error: "sub... not defined"

Am i missing something?

    On Error Resume Next
        Call ClearNothing
    On Error GoTo 0

with appreciation and thnx in advance,


m.

[CJ_London]

this is a compilation error, not a runtime error - unless you have precompiled your code access will 'compile as it goes'. So the called function needs to exist.

No idea why you are deleting a module, but if you are, you need to delete the calling code as well.

If you compile then delete the module or make any change that impacts compilation for that matter, the code becomes uncompiled so you are back to square one.

[davegri]

You could create a new function that always exists to call ClearNothing. If ClearNothing does not exist, you can trap it in the new function to do nothing.

Edit: I tried that and you can't trap the error. Instead of trapping the error the new function would need to scan for the module name as below.

Option Compare Database
Option Explicit


Public Function Wrapper()
    Dim i As Variant
    ' iterate thru modules
    For Each i In CurrentProject.AllModules
        If i.Name = "MyTransientModule" Then
            ' module exists, so call function in that module
            Call ClearNothing
            Exit For
        End If
    Next i
End Function

[CJ_London]

interesting solution - just tried it and I get the 'sub or function not defined 'error when either trying to compile or executing without compiling

[moke123]

Have you explored Microsoft Visual Basic For Applications Extensibility

http://www.cpearson.com/excel/vbe.aspx

[orange]

Mark,
Can you please describe the business issue that is addressed with your proposed set up? Perhaps provide an example or2 to clarify things.
I don't understand the "plan".

[markjkubicki]

the plan is a bit nefarious
I work in a small niche industry, taught myself ACCESS / code / VBA, and wrote a continuously evolving project (on my own time) that is used extensively within our office (and could easily be extended industry-wide). I plan to retire soon. Sadly, the evolution of the project will come to a screeching halt

On that first day that I am gone, I'd like the software to open with a splash "good-bye, it's been nice knowing you..." form (maybe with a bit of dark sarcasm -which i am know for). The image would hang around for 5-10sec +/- and then go away... never to be seen again (just like me!) After that happens, I would like all traces of that event to go away (the splash, not the code) (even though, trust me when i say, there is no one in the office with even the smallest bit of interest in writing code...)

delete the form,
delete the table (which contains date and time info -when to start using the form as the splash image),
delete the module that contains the code to execute...


(Each user has their own 'front-end')
___________________
behind the main menu:

        
    On Error Resume Next
        Call ClearNothing
    On Error GoTo 0

___________________
in the code module

 Sub ClearNothing()
    blnItsTime = DLookup("CloseDate", "tblNothing") < Now()
    If blnItsTime Then
        DoCmd.OpenForm "frmNothing" 'form is popup / modal / acDialog: code 'should' pause until the form is closed
        DoCmd.DeleteObject acForm, "frmNothing"
        DoCmd.DeleteObject acModule, "modNothing"
        DoCmd.DeleteObject acTable, "tblNothing"
    End If
End Sub

___________________
behind the form (popup, modal, acDialog)

Private Sub Form_Open(Cancel As Integer)
    Me.TimerInterval = 7500      '1000 = 1 second
End Sub

Private Sub Form_Timer()
    DoCmd.Close acForm, Me.Name
End Sub

[Minty]

A sort of "this tape will self destruct in 15 seconds" moment then
It's a bit of chicken and egg scenario when you start thinking it through though.

Allow me to cogitate with a beer this evening and try to work something out.

[davegri]

interesting solution - just tried it and I get the 'sub or function not defined 'error when either trying to compile or executing without compiling

If you're referring to post #3, that's odd. No errors at all and it works perfectly as expected for me.

[CJ_London]

If you're referring to post #3,

yes, just copy/pasted your code - I also tried removing option explicit and changed the error handling to Break on Unhandled Errors (I usually have it set to Break in Class Module) - could not get it to compile or run.

[davegri]

yes, just copy/pasted your code - I also tried removing option explicit and changed the error handling to Break on Unhandled Errors (I usually have it set to Break in Class Module) - could not get it to compile or run.

You are correct. My testing technique was faulty. Instead of deleting MyTransientModule, I changed its name. That simply left function ChangeNothing intact in a different module instead of destroying it.

[markjkubicki]

"this tape will self destruct in 15 seconds"

... EXACTLY !

[Welshgasman]

And could easily be used to delete valid code as well? if perhaps you were being sacked?

[Minty]

And could easily be used to delete valid code as well? if perhaps you were being sacked?

There's easier ways than this... #cynic#

[Welshgasman]

I worked at one place where a manager was not sacked, but was leaving as he was refused a pay rise.
He chamged all the passwords on the VAX system, that they had to get VAX in to be able to use the system again.

If you think about it, it would be pretty untraceable?

Not saying that is actually the case here, else why say it's purpose, but still.....