Traditional client-server system, then. High uptime but low resource
utilization. Row Concurrency could become an issue if you don't tend to it.
Scalability is not much of a concern at 20 users. Are we on the same page?
I'd suggest that you would be best off stored procedures for Insert, Update,
and Delete of the information you want in row format, and then use data
adapters to retrieve and return the information to the database. (You can
create the data adapter using the wizard and enter in the names of the
stored procs there).
Architecturally, make each client communicate directly with SQL Server. At
the end of the day, if you attempt to pass tables to remote objects running
on the server and then use SQL INSERT from there, you will add more
complexity than you will save in throughput. (I'd wager that throughput
could drop, but is unlikely to increase... so there's little reason to do
this).
As for the relationships between questions: provide data fields in database
to declare the relationships, return them in the dataset, and interpret the
relationships, in terms of GUI behavior, at the front-end. This can be a
simple foreign key field.
I hope that this helps to answer your question. If not, please let me know
where I'm off track and I'll try again.
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"gv" <vi*****@musc.edu> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
SQL 2000 is on a Server.
Rich client Interface
Only connect to log in and, to save or get data.
about 20 people total
thanks
gv
"Nick Malik [Microsoft]" <ni*******@hotmail.nospam.com> wrote in message
news:wI********************@comcast.com... I'd love to know why you want the most efficient mechanism... because I'd
turn around and ask: efficient under what conditions?
a) is the SQL Server a desktop edition (or CE) or is it shared by many
folks on a server?
b) is your application a web app or does it have a rich client (windows
form) interface?
c) are your users always connected to the network that contains the SQL
Server, or can they use your app in a disconnected state?
d) how many users will use your app at the same time? Will that number
grow? What's the maximum foreseeable number of users that you want to
pay for right now? (The larger the number, the more expensive the
solution, so don't say "unlimited." Even eBay has a limit.)
These things matter. Depending on your answers, you will get some pretty
different advice.
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"gv" <vi*****@musc.edu> wrote in message
news:O3**************@TK2MSFTNGP09.phx.gbl... Hi all,
I need to store values in a client application then later when done send
them to SQL 2000.
I know there is several ways to do this but, looking for the fastest ,
and most effient way to
do this? Would a global array be the best way to this and could I use
this
with mulitple values for each question? There might be over 50 different
questions.
I would need to Save, Edit before I send. And one more tricky thing.
Some of the question
go with other questions. I would just also need a way to track the
relationship between those questions?
Example: Need to store the following
Q1 = A
Q1 = C
Q1= G
Q2 = rr
Q2 = 4598
Q2 = SSS
If a Global Array or Array list is good can someone please show example.
thanks for any help
Gerry