J
John
Hi
I have a 10 user access backend/front end app which runs sufficiently ok.
Recently I deployed a winform/ado.net app that runs a sequence of queries on
the access backend db using OleDb ExecuteNonQuery method.
Problem is some users have started reporting frozen front end access app. I
can not say for sure that my ado.net app is responsible but problem seems to
have come up in the same time frame. Is there any way I can avoid this sort
of blocking and specifically if I can have a shorter timeout period for
queries if a record/table is being used and can not be made available to the
query?
Any other ideas to help the situation would be much appreciated.
Many Thanks
Regards
I have a 10 user access backend/front end app which runs sufficiently ok.
Recently I deployed a winform/ado.net app that runs a sequence of queries on
the access backend db using OleDb ExecuteNonQuery method.
Problem is some users have started reporting frozen front end access app. I
can not say for sure that my ado.net app is responsible but problem seems to
have come up in the same time frame. Is there any way I can avoid this sort
of blocking and specifically if I can have a shorter timeout period for
queries if a record/table is being used and can not be made available to the
query?
Any other ideas to help the situation would be much appreciated.
Many Thanks
Regards