macro condition clause help? 1

[larryww]

When you open up the condition column in (A2000) macro design, you can put a UDF (or other function that returns True or False) whether to execute a macro statement(s). I've seen examples with IsNull().

How would I condition based on whether a table exists, such as IfExists(tblFoo)? IsObject didn't seem to do the trick.

The objective is to prevent the warning when I do a DeleteObject Action on a table that doesn't exist. Amazingly enough, SetWarnings to No does not stop this error message.

 

[RickSpr]

Your IfExists() function is actually the best way to do it. You just need to create the function.

Create a standard module and enter this function into it:

    Public Sub IfExists(TableName As String) As Boolean
        Dim tdf As DAO.TableDef

        On Error Resume Next
        Set tdf = CurrentDb.TableDefs(TableName)
        IfExists = (Err = 0)
        Set tdf = Nothing
    End Sub

In your macro condition column, put:
IfExists("tblFoo&quot Rick Sprague

 

[larryww]

Thanks, Rick. I hoped to avoid a UDF, but since it looks like I must, that's a pretty tight and clean yet fully explicit explanation (wtg! May all my questions be answered thusly LOL).

I tried various things in the condition column:

[currentdb].[tabledefs]("tblFoo&quot.[RecordCount]>=0
[currentdb].[querydefs]("query1&quot.[myCount]>=0
(Query1 produced a field Mycount from tblFoo).

I also tried variations of IsObject() and IsError() but the irritating part was the impotence of SetWarnings to No.

Still, very nice and accurate answer.

 

[larryww]

BTW, oops - looks like that function is wearing a Sub coat

 

[RickSpr]

You're right--but you knew to change it to Function, right?

BTW, the reason the Set Warnings doesn't work is that the message is an error, not a warning. Errors occur when a requested action simply can't be done. Warnings occur when it can be done, but has potentially harmful consequences. So deleting an object that isn't there is an error, while deleting one that is there is a warning. Rick Sprague

 

[larryww]

Solution achieved:
DCount(&quot;*&quot;,&quot;MSysObjects&quot;,&quot;type = 1 and name = 'tblFoo'&quot<>0

Works right there in the condition column