Production report

[Shri]

Hi all,

I have a production report where multiple users have access to the report.
The production report is created off of make a table query. The DB has a main
menu where the users can select the specific report and preview it before
they print it.

The issue with the report is when user1 is in the production report and
previewing it and user2 tries to access the same production report at the
same time, the user2 gets the production of user1 instead of his own
production.
Is there any way I can disable the preview button and print button on the
main menu for user2, when an user1 is in the report. If so, could anyone
please let me know how can I code that.

I appreciate all your help.

Thanks

Thanks.

 

[Allen Browne]

Split the database, so each user has an independent front end.

If that's a new concept, see:
Split your MDB file into data and application
at:
http://allenbrowne.com/ser-01.html

 

[Shri]

I haven't tried splitting the DB as it is little bit confusing. I just wanted
to know if there is any other way I can avoid the issue by using the event
procedures.

 

[Marshall Barton]

I have a production report where multiple users have access to the report.
The production report is created off of make a table query. The DB has a main
menu where the users can select the specific report and preview it before
they print it.

The issue with the report is when user1 is in the production report and
previewing it and user2 tries to access the same production report at the
same time, the user2 gets the production of user1 instead of his own
production.
Is there any way I can disable the preview button and print button on the
main menu for user2, when an user1 is in the report. If so, could anyone
please let me know how can I code that.

That's just one of the complications of using make table
queries. Why do you think you need to do that?

 

[Shri]

The production report is designed to pull either for a day or a week or a
month. The report has many sub queries and I need to gather the final data
from all the queries to write to a table. If I don't use make a table query
I was getting duplicate numbers.

I was thinking when the report is pulled by user1 and when user2 tries to
pull the report at the same time, if I can trigger some event procedure and
popup a message "The report is opened by another user" and disable the
preview button for user2 in the main menu. This may avoid the issue. But I
am not sure what event procedures I can use in the report.

 

[Marshall Barton]

The production report is designed to pull either for a day or a week or a
month. The report has many sub queries and I need to gather the final data
from all the queries to write to a table. If I don't use make a table query
I was getting duplicate numbers.

I was thinking when the report is pulled by user1 and when user2 tries to
pull the report at the same time, if I can trigger some event procedure and
popup a message "The report is opened by another user" and disable the
preview button for user2 in the main menu. This may avoid the issue. But I
am not sure what event procedures I can use in the report.

Your make table query uses a SELECT statement to specify the
records to put in the new table. You should be able to use
that SELECT statement as the report's record source anf
avoid this particular multiple user problem. If that
produces duplicate records, try using the DISTINCT
predicate.

OTOH, most of what you are saying tells me that your
database design has bigger problems than just this issue.
Allen's atatement about splitting the database is a
fundamental concept that applies to just about any database,
even ones for a single user. An unsplit copy of the
database on a server is a disaster waiting to happen (at the
worst possible time ;-)

It sounds like the way your database is being used requires
you to redesign it from scratch. I gather that you are not
in a position to do that so you might be better off just
using Tools - Options - Advanced to require Exclusive use of
the database.