What is the proper way to make the app issue a warning sound (a beep or similar)? I know of three ways:

- Utility BEEP

- Msg with "N…" in the type field (field 2) and some number in the BEEP$ field (field 22)

- Use the Win Api MessageBeep function directly.

But here is the real question. No matter which way I try - after a beep is sounded it takes some time (a second or two) before the next one will be audible. So if the app issues several beeps per second only some of the beeps will be heard.

It's the same with OpenInsight itself. For a demonstration try to do the harmless exercise of attaching a set of already attached tables with Database Manager. You will get a warning with a beep for every table. But if you click the OK buttons fast enough (well, it doesn't have to be that fast), only every second beep will be heard.

I can live with that (i.e, with DM being tongue-tied), but now I have under development this key-driven interface where the key-clicks can come thick and fast, and I want my app to beep for all the invalid keystrokes.

Please help.

- Oystein -

Øystein Reigem,

Humanities Information Technologies,

Allégt 27,

N-5007 Bergen,

Norway.

Tel: +47 55 58 32 42.

Fax: +47 55 58 94 70.

oystein.reigem@hit.uib.no

Home tel/fax: +47 56 14 06 11.

Oystein-

If your system is using the MS Default beep, it is a wav of .524 seconds, but only contains sound for about .3 seconds- .2 seconds is dead air.

Have you tried a different wav of full sound, with a shorter duration?

Hope it helps-

Mike Ruane

Mike,

Thanks a lot!

After I made the posting it occurred to me that was the explanation, but I hadn't come around to checking it out yet.

Perhaps Revelation too should opt for a briefer sound?

- Oystein -

O-

I believe they just make calls to MessageBeep.

View this thread on the Works forum...