our problem exist somewhere in hitting the Enter Key on a message box. I realize the problem is within the database; however, it has something to do with the Citrix connection. When we run the database runs from local C drive, there is no beep. It does not occur until we place the DB on the Citrix server.
I am still trying to figure how to shut off the beep through code - any assistance is deeply appreciated.
There is a method of the DoCmd object called SetWarnings that can be turned off (and must be turned back on!).
Will this help? Otherwise you could always set the Citrix on fire......
It's always darkest before dawn. So if you're going to steal your
neighbor's newspaper, that's the time to do it.
Thanks for your reply! Unfortunately, the DoCmd is not the issue.
The issue is a combination of MS Access and Citrix. There is a system "Beep" sound when the message box pops up and the user is connected to Citirx. The database code reacts differently when the database resides on my computer than when it resides on the Citrix server. When a user is connected to Citrix and preforms a particular application function (Clicks on Message box) the system "beeps" But if the user preforms the same function on their local machine it does not beep.
The database is called TestBeep.mdb. In the database, there is 1 form with 5 buttons. Use the TestBeep database on Citrix and then copy the database on to my PC. there is no beep when the database resides on your computer.
Here is another strange thing. When I write the msgbox code in a Macro and disable the Beep - there is no beep on Citrix or on my computer. However, when convert the code from a macro to VB - the beep returns. The messages are too complex to use them as macros. Maybe you know how to adjust the converted code. Thanks alot!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.