MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

SharePoint and Access

  Asked By: Hiral    Date: Dec 08    Category: MOSS    Views: 1298

Has anyone created an Access database that was accessible through
SharePoint? We would like to create a database in SharePoint that is a
little bit more complicated than a typical list. We first thought to
create an SQL database, but then thought an Access database might work



13 Answers Found

Answer #1    Answered By: Alisha Itagi     Answered On: Dec 08

Go with a SQL solution. Access does not work with SharePoint. Besides, Access
can only be opened by one person at a time.

Answer #2    Answered By: Maricela Conway     Answered On: Dec 08

Access 2007 integrates with Windows sharepoint  Services 3 (WSS) and
Microsoft Office SharePoint Server 2007 (MOSS) on many different levels.
You can store access  data in SharePoint lists and you can use Access to
take SharePoint data offline

i.e. the basic premise is that you can use access as a front end to MOSS
- indeed, you can create  all of the data in access and then use it to
publish that data through to sharepoint or move your current access
based solutions through to sharepoint

What I don't think you can do is do it the other way round like you are
asking - i.e. take from sharepoint and push to access or use sharepoint
as a front end to data held in access

Generally, the answers that you have been given are entirely correct -
use sql  to create your database  solution and then use SharePoint custom
web parts to enter data into that database and sql reporting via
sharepoint to report on it etc

Answer #3    Answered By: Vinay Thakur     Answered On: Dec 08

In MOSS, create  a BDC connection to access  it. This
requires MOSS Enterprise.

Answer #4    Answered By: Caleb Gordon     Answered On: Dec 08

It sounds like you'll be developing a user interface from scratch. You
may have suggested access  so that you could use it to quickly develop
this interface. I don't believe that Access applications can be 'plugged
in' to SharePoint.

I would suggest that you consider breaking the solution down into three

1) Design and develop your data model and database. The Access back-end
(Jet) might be ok for this, but since you already have MSSQL I'd
recommend using it instead.

2) Develop a web service interface to your database.

3) Develop your user interface in SharePoint. This might involve custom
web parts. sharepoint  would access the database  through the web service

I wish I could give you guidance on how to approach steps 2 and 3, but I
have yet to do it myself. Hopefully someone else here can guide us!

Answer #5    Answered By: Micheal Knight     Answered On: Dec 08

I have an Access database  that is linked to Sharepoint. Starting with
Access 2003, I think it was, you can link directly to Sharepoint
tables. Just choose "Windows Sharepoint Services" as the file type
when you go to link your tables. You can also import Access tables
into Sharepoint, but this method just creates a static copy of the data.

By linking Access to Sharepoint, you're still limited to your basic
Sharepoint "list." But you can create  additional Access tables that
refer to the primary keys on your Sharepoint tables, run queries,
update data in the Sharepoint tables just as you'd update an Access
table, all that stuff, to end up with something fairly fancy.

Answer #6    Answered By: Judy Pittman     Answered On: Dec 08

More than one person can use the Access db at a time. I have
an Access db linked to Sharepoint that's being used by four people as
we speak.

Answer #7    Answered By: Joanne Greer     Answered On: Dec 08

What happens when eleven people try to use the Access db at the same time?

Answer #8    Answered By: Cathy Cameron     Answered On: Dec 08

I've had Access databases with 50 simultaneous users with no problem.
Of course stuff like that always depends on how you build the database,
how much data you have, how many people are likely to be writing to it
simultaneously, etc.

People underestimate how robust Access can be in a multiuser
environment, I think, maybe because Access databases can be developed
by folks at a lot of different levels of experience. If you use good
relational design, and split it into a front end and back end, you're
pretty much home-free in most small group settings. Put some extra
thought into transactions and record locking and such, and you can run
the world! Okay, maybe not... but it's really an excellent option for
lots of small group applications, in my experience.

Answer #9    Answered By: Kerri Steele     Answered On: Dec 08

I was trying to think of a funny response, but couldn't come up with
one. I know that Bob was asking a serious question, but for some
reason, when I read it, I heard it in the vein of "how many <insert name
of group here> does it take to screw in a light bulb?".

Answer #10    Answered By: Alisha Itagi     Answered On: Dec 08

That must be with Access 2007.

Answer #11    Answered By: Vinay Thakur     Answered On: Dec 08

There are major changes to access  2007 especially as regards its
integration into sharepoint

Answer #12    Answered By: Judy Pittman     Answered On: Dec 08

We're actually using Access 2003, and linking to Sharepoint is pretty
straightforward with that version. We used to have 2000, and it was
more of a pain, not really worth the trouble IMO... Haven't gotten to
try 2007 myself, will be interesting to see what's been added...

Answer #13    Answered By: Micheal Knight     Answered On: Dec 08

Three of us. "How do you keep a <Insert name of group> in suspense?

Didn't find what you were looking for? Find more on SharePoint and Access Or get search suggestion and latest updates.