When my application is distributed it will have no records. However, when the ONSTARTUP script is run it sets ErrorCapture ON and UserAbort OFF. But if the user clicks anywhere on the layout (besides the 'add new member button), it produces this dialog.

Question: "how can I suppress this message?"

Thanks

Ron

Why not have your startup script create a new record, then give the user the opportunity to delete it and exit the application later on? I assume that since your script directs the user to this layout, it must be important. What's the point in having no records?

Why not have your startup script create a new record, then give the user the opportunity to delete it and exit the application later on? I assume that since your script directs the user to this layout, it must be important. What's the point in having no records?

When I distribute the application, it only shows a few sample records. (It is a membership database). The user will want to input his sown records. To that end, I provide a "Delete all members" menu option which deletes all the records.

Yes, I could script a deletion of all records and then just add a 'dummy' record. But I would be in the same problem if the user just deleted the dummy record.

I have debug on and this FM message appears without any debug awareness of a process that causes it. So, the question remains: "Isn't there some way to avoid having this message appear?"

There is a method that involves putting a web viewer over the layout background.

But why suppress it? This is an error that users will see ONCE in their entire use of the database, and it's also an accurate description of the problem. :)

Why suppress it?

For one thing, I have a custom menu that does NOT have a 'New Record' menu choice. (Yes, I can add one. But that would defeat the learning experience I am trying to have )

Second, I got 'around' it putting some 'record count' code in the layout load of the generating layout and when it is 0, I put up a friendly dialog that explains the situation. So, problem solved.

But, isn't it weird that FM "*MANDATES*" this dialog? Without a way for the developer to suppress it (easilly).

Ron