Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Beeps

edited March 2002 in General
Hello Digital Metaphors

My D6Pro application uses RBEnt 6.03 with a patch from DM repairing a
problem, RP6.03 forgot to switch printers when a user selected printer,
after preview to screen, different than the default printer.

My application is organised by Delphi forms and each Delphi Form has a
single RB Report using a Paradox table.

The reports are kept in a database and are loaded as required.

I have the following problem with some Delphi Forms/Reports:

When the pardox table has any operation in code done on it (open, close,
CheckBrowseMode) the PC somewhere causes the Windows Default Beep sound to
be played. This happens in Win2000 and XP at least. I know its the Default
beep because changing the default beep WAV file changes the audio output.

Nowhere in my code do I call "beep" or messagebeep(0). I scanned RB Code and
found calls to messagebeep in a toolbar module but this code is not called
in my app.

I think the error is associated with the report as the beeps happen when the
report is generated and when developing if I ask for a preview from the IDE.

The error is not, I believe, in the BDE. Another app using the tables, with
no reports, does not have the problem.

When, for example, I do a tabelName.CheckBrowsemode; none of the
eventhandlers listed for the associated report are called. The associated
pipeline has no events. But the beeps happen. During the execution of
CheckBrowseMode many calls are made to ppClass.TriggerCodeModuleDestroy, but
I have not yet found an error or where be beep is called.

I also have not yet found the difference between the Delphi Forms where
beeps do and do not happen.

In short I am lost and wonder if you can gove me any insight?

Many thanks

Russell

Comments

  • edited March 2002
    Hello Digital Metaphors

    Please disregard my question. The root of my error is associated with a
    RichText control containing protected text.

    Regards

    Russell


This discussion has been closed.