Multi User Access Problem with printing reports

[Liz_I3]

I have a multi user (about 8) Access 2000 DB. IF two users happen to request the same report at almost the same time only the second request is printed twice. It is a if the queries parameters change before the first request is printed and so prints the second request twice. If you wait a few seconds before sending the second request both reports do print correctly. Is there a way I could pause the query for a second or two before it excepts the next set of paremeters?

Thanks
Liz

 

[mdmilner]

One possibility is to drop in a coded wait command.
Not sure if this would fix your problem though. Depends on how it's coded.
Sure sounds like the report is based on the contents of a query or table records and other users have the ability to change those records before the database is done with the print request.

Private Declare Sub sapiSleep Lib "Kernel32" _
        Alias "Sleep" _
        (ByVal dwMilliseconds As Long)

Sub sSleep(lngMilliSec As Long)
    If lngMilliSec > 0 Then
        Call sapiSleep(lngMilliSec)
    End If
End Sub

DoEvents might be an option also (in Access Help)

Mike

 

[Liz_I3]

Hi Mike thanks for your assistance

You are correct the report is based on an SQL query that requires the user to input 2 parameters and team number and a date.
So yes if an other users request the report with a different team number, the records or query changes before the database is done with the first print request.

So what would work best the wait command or the doevents?

Thanks again
liz

 

[mdmilner]

I haven't really tested, but I've read that DoEvents doesn't always do what it's supposed to do.

What I'm thinking is pretty involved - by that I mean there may be a simpler method but I'm not sure what it might be offhand.

What you could try is this: Save the current status of your print requests as a record in a given table. Aka, user issues a print request and it changes a value in a table that pretty much says "I'm busy" and changes it back once it's done.

Each new print request would probably need to sorta go into a queue - re-issue the request every so often until the database is 'available' but after a set period of time to go ahead and print away.

Some good ideas on methods over at www.accessweb.com and www.fabalou.com

Mike

 

[bat17]

Another option is to create seperate front ends for your users, more work when you are updating, but less prone to problems.

HTH

Peter

 

[Liz_I3]

Thanks for all the help
I was told that I should put a edit Lock on the query. Does this make sense ?

Liz