SQL Server or Sharepoint?

On Wed, 8 Jul 2009 19:40:01 -0700, Nurse Nancy
wrote:

I have built a sharepoint site for them via APTIX hosting. Right now the
Access DB is in one piece and resides in a document library in sharepoint.
Only 2 people are using it and they area able to check it out and enter their
data and run queries, reports by taking turns.

I thought Sharepoint could be used to share the DB,, and allow multiple
people to use, update the DB at the same time via active directory but it
doesn't look like that is allowable.

Soon the other 9 people will need acess. I think sharepoint is the best
option for them since they are already paying for it.

When i export the files to lists, can the queries and reports remain in the
access db? Would i give each person a copy of the DB to run locally and link
to the tables in Sharepoint?

I don't have A2007 available at the moment, but my understanding is that you
can use File... Get External Data... Link to link *to a Sharpoint list* as a
table. Storing the database file in a document library is a different
operation; what we're proposing is that each user would have their own
separate copy of an Access database (the "frontend") with links to the
Sharepoint list on a central server. The list would contain the data, and
users could read or update it from their own frontend.
--

John W. Vinson [MVP]

=?Utf-8?B?TnVyc2UgTmFuY3k=?=
wrote in :

I think sharepoint is the best
option for them since they are already paying for it.

But if it can't do what you want and requires re-engineering your
Access app, what good is it to save the money?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Thanks John,
I will test this out next week and let you know..
Is splitting the database a viable option, or is that what was done before
sharepoint was built?
Nancy


"John W. Vinson" wrote:

On Wed, 8 Jul 2009 19:40:01 -0700, Nurse Nancy
wrote:

I have built a sharepoint site for them via APTIX hosting. Right now the
Access DB is in one piece and resides in a document library in sharepoint.
Only 2 people are using it and they area able to check it out and enter their
data and run queries, reports by taking turns.

I thought Sharepoint could be used to share the DB,, and allow multiple
people to use, update the DB at the same time via active directory but it
doesn't look like that is allowable.

Soon the other 9 people will need acess. I think sharepoint is the best
option for them since they are already paying for it.

When i export the files to lists, can the queries and reports remain in the
access db? Would i give each person a copy of the DB to run locally and link
to the tables in Sharepoint?

I don't have A2007 available at the moment, but my understanding is that you
can use File... Get External Data... Link to link *to a Sharpoint list* as a
table. Storing the database file in a document library is a different
operation; what we're proposing is that each user would have their own
separate copy of an Access database (the "frontend") with links to the
Sharepoint list on a central server. The list would contain the data, and
users could read or update it from their own frontend.
--

John W. Vinson [MVP]

On Fri, 10 Jul 2009 03:34:06 -0700, Nurse Nancy
wrote:

Thanks John,
I will test this out next week and let you know..
Is splitting the database a viable option, or is that what was done before
sharepoint was built?
Nancy

Splitting the database IS NOT a viable option for wide-area networks.

First choice: use Citrix or Windows Terminal Server to give users a remote
terminal to log on to a central server containing a split database. Each user
would have a private folder with their own copy of the frontend.

Second choice: use SQL/Server as the backend. If you have a corporate SQL
instance talk to your DBA.

Third choice: Sharepoint. New, limited (no referential integrity), and I have
no direct experience with it.
--

John W. Vinson [MVP]