Access 2007 database hosted on Share Point 2007 server

H0MELY

unread,

Jun 15, 2007, 3:25:01 PM6/15/07

to

I would love to see an example of an Access 2007 database hosted on a Share
Point 2007 Server. I hear thatyou can actually host the database on the
Share Point Server...but I would love to if all of the functionality is truly
there, most importantly Forms. If anyone knows of an example that I could
check out...that would be FANTASTIC!!!

Steve Schapel

unread,

Jun 16, 2007, 4:51:48 AM6/16/07

to

H0MELY,

I don't think it is as you envisage. Yes, you can publish an Access
2007 database to a SharePoint site. This makes the application
available to anyone who has access to the site. *But*... it is really
just stored in a document library on the site. To use the application,
as an Access frontend, it gets downloaded to your local machine, and
still runs under the Access 2007 installed on the local machine.

--
Steve Schapel, Microsoft Access MVP

H0MELY

unread,

Jun 18, 2007, 10:41:01 AM6/18/07

to

Steve, thank you for the response. Basically I have previously setup a data
access page for users to access a database on a shared drive...but
unfortunately the database is pretty big (980K after compacting) and the
shared drive is VERY VERY slow. The data basically holds information on how
money is being spent. I want the users to be able to search the spend and
also assign a particular vendor to a team member. I have also had issues
with the absolute address. Anyway...What I am really wanting to do is share
the content of the data to users in a fast environment...our sharepoint
server is much speedier than the shared drive, I have tried to use linked
tables and lists but it doesn't really allow the GUI interactivity and the
ability to display related data from multiple lists. So...that is where I am
and what is driving me...you said in your response that a copy of the
database would be downloaded and run on the users machine...which basically
makes me think that sharepoint is not the answer. Any suggestions that you
would have would be greatly appreciated. Again I totally apologize for the
personal email...I am unfortunately being pressed for options right now. I
am not necessarily a database expert...I have just made the mistake of
accomplishing everything I have been asked to do in the past. Thank you
again for the information, I am anxious to hear any replies.

-John

Steve Schapel

unread,

Jun 18, 2007, 5:59:11 PM6/18/07

to

John,

I'm not sure whether your 980K was a typo. 980K is pretty small. 980
MB is pretty big.

You are talking about a LAN here, right? So the 'Shared Drive' is on
one of the machines on the network? Or a server to which all the users
are locally connected? So why is it very very slow?

What you need is for your application to be split into a backend with
the core data tables, and a frontend application file with all the other
Access objects (forms and reports etc). And for each user to have their
own copy of the frontend installed on their own computer, and all
linking via the network to the backend tables, of which there is only
one copy on the server. This is the "standard". Is this what you have now?

Tom Wickerqueer

unread,

Jun 25, 2007, 4:54:54 AM6/25/07

to

I'd recccomend DREAMWEAVER and getting as far away from Access as possible

"H0MELY" <H0M...@discussions.microsoft.com> wrote in message
news:682CB7A8-28CD-4916...@microsoft.com...