Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Deactive "Debug" button when run-time error

Status
Not open for further replies.

TorF

Programmer
Sep 30, 2002
83
FR
When a run-time error is produced, a message box appears and propose to "End" program or to "Debug".

Is it possible to deactive this Debug button ?
Because i don't want the users easily going into code just by clicking on this button.
If possible without using the "On Error..." procedure, or maybe juste 1 time in all code.

Thanks


 
I think changing Tools-StartUp-Advanced Allow Viewing Code After Error to unticked will do it.

There are two ways to write error-free programs; only the third one works.
 
Ok...
In my Access 2000 version there isn't a such "Tools->StartUp->Advanced->Allow Viewing Code After Error" control... grrrr
 
Oh! Okay, try searching the help for 'AllowBreakIntoCode' you may be able to set that property from code.
Although, this may also be a AC97 thing.

There are two ways to write error-free programs; only the third one works.
 
I alwas use mde's for my users... what this does is it allowes me to develop in my mdb, and when i'm ready to put out a change or some thing into the mde, I just compile it into an mde...

MDE is a compiled vertion of a database... it is not possable to even see the code in an mde, so if you want to go this route be very carefull with your mdb...

--James
junior1544@jmjpc.net
Life is change. To deny change is to deny life.
 
Yes GHolden, help talks about AllowBreakIntoCode, and i add this property to database using this function :

Public Sub MyAddProperties()
Dim prp
Set prp = CurrentDb.CreateProperty("AllowBreakIntoCode", 1, False)
CurrentDb.Properties.Append prp
End Sub

But in fact there is no changement :/


========
YES junior, MDE is a good solution and that works :)


Thanks all
 
MDE is a much better way to go anyway....

There are two ways to write error-free programs; only the third one works.
 
oh yea, another thing about MDE's... they run faster because all the code is already compiled...

just a side note:)
--James
junior1544@jmjpc.net
Life is change. To deny change is to deny life.
 
And they are less prone to corruption.


There are two ways to write error-free programs; only the third one works.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top