Run time errors have stopped in Access '03

[E Scrubb]

Hi all - this is driving me nuts - the runtime errors in a particular
database seem to have been turned off. The following code is the a test
module:

Private Sub test_Write()
DoCmd.SetWarnings (True)
Dim cnn As ADODB.Connection
Dim rst As ADODB.Recordset
Set cnn = CurrentProject.Connection
Set rst = New ADODB.Recordset
rst.Open "something", cnn

Debug.Print "we're inside"

The database that I've created has no table or query named 'something'
yet I receive no errors from access when trying to run this code - nor
does the debug.print ever get executed. I have set the Tools->Options->
General to 'Break on All errors' and still I get no response from this
code.

Interesting enough, when I use this code in any other database - I
correctly get a set of errors letting me know that 'something' either
doesn't exist or isn't a valid SQL statement - any help would be
appreciated - thanks, Neal

 

[dbahooker]

it is an option under 'tools, options'

'break on unhandled errors, all errors, no errors'

right?

-aaron

 

[E Scrubb]

it is an option under 'tools, options'

'break on unhandled errors, all errors, no errors'

right?

-aaron

Unfortunately, no - I tried that and still the same thing - any other
ideas?

 

[dbahooker]

are you sure your code is running?

i mean.. could it be that 'macros are disabled' altogether?

 

[E Scrubb]

are you sure your code is running?

i mean.. could it be that 'macros are disabled' altogether?

no - unfortunately - Macros are my only work around right now - they
seem to work fine - its the code that I cannot get to run. I do know
that it runs because if I place my debug.print statement at the start of
the procedure it will print in the immediate window - thanks in advance
for your help - neal

 

[dbahooker]

the code you cannot get to run??

no modules run at all?

from the access 2003 Window, tools, macros, security, set it to low or
medium?

when you open this app; exactly which prompts do you get for security??

it's like.. if you hit 'disable macros' then modules won't work

btw, who in the heck is the fat drunk product manager at Microsoft that
named Macros and Modules?

who decided that to set security on a module; that you need to go
tools, macros?

who is it that decided to prompt you with a box that says 'enable
macros' or 'disable macros' when they're really referring to modules?

-aaron