Unwanted records

[Homegrownandy]

I have a data entry form. When opened it creates a new record by default. I have disabled the navigation buttons and form close buttons and put in my own command buttons. The user can click exit without saving and it will run a query to delete that record.



However, If the whole database is closed and this form has been opened it creates a situation where we have blank records that will appear on reports and are useless.

How could i prevent this?

Thanks in advance.

[orange]

If the whole database is closed and this form has been opened it creates a situation where we have blank records that will appear on reports and are useless.

??? The database is closed and the form is open??? I'm missing something..

Perhaps some routine on the database close that purges/deletes records that can be identified.

[Homegrownandy]

No thats right, the database can be closed with forms open at the time. This then bypasses all exit proceedures. Thats the issue.

I cant stop someone closing the frontend of their database.
I cant have a delete query on the close event of the form as this would happen on records we want to keep.
I could add a message box to ask if they want to delete the record but this would happen every time and be confusing.

[orange]

Are there multiple conditions here?

User closes the front end, is not working with a form
User closes the front end, is working with a form and has not completed the process
User closes the form, but front end is still open
others??

[Gicu]

Why don't you silently run the delete query to remove empty records when you open the application (in the OnOpen or OnLoad code of your opening form or with an AutoExec macro) and also in the Unload event of the main form. If you do not have a main/switchboard type form you can create a small form that you keep hidden and use its Unload event to run the delete.
https://www.access-programmers.co.uk...-event.213758/
Cheers,

[Homegrownandy]

Thank you. Most of the entry is automatic but i've made it so the user must enter a date before they can click the subform. I can now run the delete query based on there being no date.

This isn't fool proof. But it does help.

It's possible someone opens the form to enter data, whilst someone else triggers the delete query (deleting the current record). Ill have a think about it but this is an improvement.

Thank you.

[Micron]

This "new record" must not be created by using default values, otherwise there would be nothing to save. You must be populating the form fields directly based on form load code or something. That's the root of your problem.
If you can't eliminate the application close button, I see no way around not using default values except for requiring at least x fields to be not null upon form unload, and if they are, delete the record. Or you could set a flag if the form close button is used, thus if the db close is invoked, the flag is false, thus delete the record. To me, any of this seems like a hack when you could used default values - either in the table design or by setting the property on form load.

[Homegrownandy]

Thank you for your input. Interesting ideas.