Re: Multiuser local and server tables
- From: "John Spencer" <spencer@xxxxxxxxx>
- Date: Fri, 1 Sep 2006 09:27:49 -0400
How about just adding another field to your two input tables?
Store the requesting user in the field.
When the user wants to run another report/query, then you clear out the old
records by user name.
You will also have to modify all the queries that use this information, but
that can be done.
"BillyRogers" <BillyRogers@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0C06AC6E-DDC2-4835-9CBA-7848F8D038B7@xxxxxxxxxxxxxxxx
I meant "Views" instead of "Stored Procedures" . the report uses linked
views and tables on SQL Server
--
Billy Rogers
Dallas,TX
Currently Using Office 2000
"BillyRogers" wrote:
I'm in the process of trying to convert an Access database that is
currently
being used by 3 people into one that can be used by more than 20 people.
The report that is created uses linked SQL Server stored procedures and
two
SQL Server Tables that are linked to the Stored procedures. The two
tables
are used for the user input. One holds account numbers and the other
holds
the month and years that they want the report to cover.
From what i understand it is better in a multiuser environment to not use
linked tables and views, but instead to connect programmatically in code.
I've learned how to do that using ado.
The main challenge is the two input tables on the server. With so many
people using the program it's inevitable that someone is going to change
the
inputs before someone else is done using the program. My thought is to
use
local tables for the input. The number of inputs is unknown...it could
be
one account number and date or up to 30 account numbers and 12 months of
data.
My question is how to I rewrite the views to refer to the local tables?
or
is that even the correct approach? I need to connect the views to the
data
in the local tables somehow or maybe put the data in the local tables
into an
array and connect the array to the views?........This is new to me and
I'm
not sure what approach to take.
I thought about giving each user their own input tables on sql server but
that seems like a maintenance nighmare as the views that i'm using are
large
and complicated and would take a lot of time to build every user their
own
individual database.
--
Billy Rogers
Dallas,TX
Currently Using Office 2000
.
- Prev by Date: Re: Validation Controls before Closing DB
- Next by Date: Re: Emailing report data
- Previous by thread: Re: Validation Controls before Closing DB
- Next by thread: Re: Emailing report data
- Index(es):
Relevant Pages
|
