Help with events
- Thread starter Nirious
- Start date
I have this access application that gets its tables from other access files. Those tables are used in a form in this application. Here you can manipulatethe data. The form also has a button to show you some reports containing the data from the table.
Now after a report has been printed, the uses shouldn'tbe allowed to still alter the data of this access file using the form.
The problem is that every event I try to put my code to lock the tables in, happens when I print the report, as well as when I just preview it
So I'm looking for an event that happens when you print something, but doesn't happen when you just preview a report.
I hope that made sense to you.
Nirious
Now after a report has been printed, the uses shouldn'tbe allowed to still alter the data of this access file using the form.
The problem is that every event I try to put my code to lock the tables in, happens when I print the report, as well as when I just preview it
So I'm looking for an event that happens when you print something, but doesn't happen when you just preview a report.
I hope that made sense to you.
Nirious
so you have on a form a button to preview and to print the report.
Why not in the code of the print command button write some code, that disables the form once its been printed.
But the user could still print the report by previewing it, and then printing it that way.
You could have a field on each record to say whether or not that record has been preview or printed, if the record has been printed then the user is not even able to see the record, because you would filter the form to not include these records.
Hope any of this helps, let me know if you require any more help or advise
Why not in the code of the print command button write some code, that disables the form once its been printed.
But the user could still print the report by previewing it, and then printing it that way.
You could have a field on each record to say whether or not that record has been preview or printed, if the record has been printed then the user is not even able to see the record, because you would filter the form to not include these records.
Hope any of this helps, let me know if you require any more help or advise
KenHigg
Registered User
- Local time
- Today, 08:36
- Joined
- Jun 9, 2004
- Messages
- 13,327
I think M8 is on the right track. Seems the data needs to be explicitly 'Closed' by the user instead of inheriting a rather ambiguous 'Closed' state after it has been printed. How will the user know, by viewing data in the form that it has been closed and printed...
kh
kh
Similar threads
