Supressing 'no record' and/or 'table missing' errors.

[Quartekoen]

So, the main menu for my solution is just that: a menu. The user clicks the button to go to the database he or she needs. The table for the Main menu naturally has 0 records, which is fine.

The problem comes with the user clicks somewhere other than on a button. They get the windows "WHUM" and an error saying the action cannot be performed because the required table is missing.

My thought as a solution is to make a script that runs when the main menu is opened. The entire script would be:

Set Error Capture [on]

Pause/Resume [indefinitly]

Set Error Capture [off]

The problem with this is that while the script is running, the user can't switch windows, so clicking a button is pretty much useless. Is there some way to actually turn that error off, or does every button that goes to the main menu have to start that script, and every button away from the menu stop it?

Thanks for the help.

[IdealData]

The error is nothing to do with 0 records and quite clearly states that there is a table missing. (You must have deleted it).

Find out why the error occurs first and fix it that way.

[Fitch]

What is on the menu layout other than buttons? If there's no script running, and no fields on the layout, clicking on the background shouldn't do anything, unless the background is also a button that runs a script.

There is a trick of putting an empty web viewer behind your layout to keep a record from getting committed when you click outside the fields. But I don't think that is what we're dealing with here.

I don't understand the first sentence of your last paragraph: isn't the whole point of clicking the menu buttons to switch windows? The answer to the question in that paragraph is "yes," however again I think there is something else going on here. Feel free to post the menu file.

[Quartekoen]

Yeah, Ideal was right. Somehow, there was no table connected to the layout. Someone must have deleted it from the relationships table, so the layout was showing records from . This was causing the error.

I put the main menu table back in the relationship pane (it sits there alone). The error is gone, but I'm still lost as to why it was deleted in the first place. It doesn't seem to actually serve any purpose to do that.

[Fitch]

Just goes to show you it's always a good idea to check the basic things first.