Locking (1 Viewer)

f9073341

Registered User.
Local time
Today, 08:55
Joined
Mar 7, 2009
Messages
27
Hi guys,

My database is accessed by several users. When the user opens my report it first makes a table of temporary data from one query, then uses another query on that table to populate my report. The problem is, when another user wants to view the same report, I get a table lock problem - presumably because my report is bound to the fields in the table which WOULD get overwritten whenever this report is run.

Does anyone have a way around this? I thought of populating the report from a recordset, then closing the connection. But I can't even get this to work! :(

Thanks
 

vbaInet

AWF VIP
Local time
Today, 08:55
Joined
Jan 22, 2010
Messages
26,374
Has each user got a separate front or they are sharing from one point?
 

f9073341

Registered User.
Local time
Today, 08:55
Joined
Mar 7, 2009
Messages
27
They're just sharing from one front end. I would give each user their own frontend, but it's not possible given the network constraints. They wouldn't be able to link to the source. Is there a way to do this with a form? That would be just as good... as long as they can see the results of the query.

Perhaps populate the form from a recordset then disconnect the recordset from the table?
 

HiTechCoach

Well-known member
Local time
Today, 02:55
Joined
Mar 6, 2006
Messages
4,357
They're just sharing from one front end. I would give each user their own frontend, but it's not possible given the network constraints. They wouldn't be able to link to the source. Is there a way to do this with a form? That would be just as good... as long as they can see the results of the query.

Perhaps populate the form from a recordset then disconnect the recordset from the table?

The problem is caused by the database not properly set up for multi users.

You really need to split your database into a front end and back end. Then each user would have there own copy of the front end so that temporary table is not shared.
 

Users who are viewing this thread

Top Bottom