Re: Using Open Arguments in Access Report
- From: mpfohl@xxxxxxxxxxx
- Date: 22 Nov 2006 08:14:50 -0800
Simple yet effective. perfect, thank you.
Allen Browne wrote:
Split the database.
Place the temp table in the front end.
Since each user has an independent front end, their searches do not
interfere with each other.
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
<mpfohl@xxxxxxxxxxx> wrote in message
news:1164210899.342017.154790@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On second reading that question still doesn't seem clear so let me try
one more time.
Currently, my database works like this: my search form builds the SQL
based on multiple search criteria chosen by the user. The SQL then
dumps records into a table in my database. The report then opens and
one of the many joins in that report is to that table, thereby limiting
that report to the records found by the form.
However, I want multiple users to be able to use the database at once
so if two users are trying to run a search at the same time it won't
work because there is only one static table. So I want to change this
entire search process into VB code so that multiple searches can run at
once without interfering with each other.
Thanks
.
- References:
- Using Open Arguments in Access Report
- From: mpfohl
- Re: Using Open Arguments in Access Report
- From: Allen Browne
- Re: Using Open Arguments in Access Report
- From: mpfohl
- Re: Using Open Arguments in Access Report
- From: mpfohl
- Re: Using Open Arguments in Access Report
- From: Allen Browne
- Using Open Arguments in Access Report
- Prev by Date: Re: Using Open Arguments in Access Report
- Next by Date: Problems establishing layout of subreports
- Previous by thread: Re: Using Open Arguments in Access Report
- Next by thread: Re: Please help - columns in text box within report?
- Index(es):
Relevant Pages
|
Loading