Prev: Multiple Items in Listbox
Next: Covering index
From: Jonathan on 11 May 2010 16:50
thanks.

Jonathan
<sigh>There always seems to be another way to do things and at my current
skills level the other way is the better way</sigh>

"Bob McClellan" wrote:

> Jonathan,
> One method is to use a staging table that is purged and repopulated
> as per the end user's search criteria. add a column to this table:
> [CurrentUser]
> when you fire the sp...
> first: delete from YourTable where CurrentUser = @cu
> then, Insert into YourTable ( col1, col2, CurrentUser , etc.. )
> select ( col1, col1, @cu, etc... )
>
> hth,
> ..bob
>
>
>
> "Jonathan" <Jonathan(a)discussions.microsoft.com> wrote in message
> news:D1C4DECF-A7E6-4C2E-BB85-A03F83B77B7A(a)microsoft.com...
> > Hi, using Access 2003 and SQL 2005. I have an Access application that uses
> > a
> > combination of pass-through queries and dao recordsets to load forms and
> > reports. This is not an Access Project. My question is about design.
> >
> > A search populates a table with parent record IDs. I then have a bunch of
> > stored procedures that use an inner join on this table to filter records.
> > In
> > a multiuser environment what is the best practice method to ensure that
> > the
> > table of IDs is not compromised by an user's search results? For example,
> > will using a ##temp table to hold the search result IDs give the required
> > outcome?
> >
> > Any ideas or recommendations appreciated :-)
> >
> > Many thanks,
> > Jonathan
>
First  |  Prev  | 
Pages: 1 2
Prev: Multiple Items in Listbox
Next: Covering index