Form for entry by others......

[snackwrap]

There has GOT to be an easy way to do this and I am beating my head against
the wall. Access 2007....I want my simple database accessable to the other 15
people in my group. I was hoping to have a simple HTML file that I could drop
into a network share that would allow access to the database. That or a form.
What I want is anyone to be able to open the FORM and select an item from a
drop down menu ( combo box...or other options? ) and THAT selection pull data
from the linked tables or queries. All of this available on a mapped drive
each person has access to, all files will be in the same folder, I will
simply provide a shortcut to the FILE that will open the form. I dont care if
its HTML or the actual FORM itself, I just want it simple and quick from
their perspective. I do NOT need them to be able to update via the form....
simply display data based on their selection. I will maintain the data myself.


I saw Microsoft do this YEARS ago at a seminar...I think it was for office
2000 so I KNOW 2007 has to have this same functionality...I just cannot find
any instruction or methods on doing this.

Thanks all

 

[Tom Wickerath]

Hi Snackwrap,

I was hoping to have a simple HTML file that I could drop
into a network share.... I saw Microsoft do this YEARS ago at a seminar...

It sounds to me like you are describing Data Access Pages (DAPs), which were
deprecated in Access 2007. While they still work in Access 2007, Access 2003
is the last version that you can use to create DAPs.

You could create a split multiuser Access app., and set the form of interest
as the Startup form. Each user should have their own copy of the FE
(front-end) application. This document discusses this concept in more detail:

Implementing a Successful Multiuser Access/JET Application
http://www.accessmvp.com/TWickerath/articles/multiuser.htm


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[snackwrap via AccessMonster.com]

Thanks Tom, a few hours after posting this message I found out that my
organization has a Sharepoint server so I am looking at that option as it
seems to be pretty easy to setup. I am going to look into the link you
provided though as that seems to best fit what my options are outside of the
Sharepoint server. Its a shame Microsoft did away with DAPs as it was an
amazingly easy and fast process....granted, it looks like Sharepoint might be
just as easy and was probably the reason why they did away with DAPs.

Thanks again!
-jerry

Hi Snackwrap,

I was hoping to have a simple HTML file that I could drop
into a network share.... I saw Microsoft do this YEARS ago at a seminar...

It sounds to me like you are describing Data Access Pages (DAPs), which were
deprecated in Access 2007. While they still work in Access 2007, Access 2003
is the last version that you can use to create DAPs.

You could create a split multiuser Access app., and set the form of interest
as the Startup form. Each user should have their own copy of the FE
(front-end) application. This document discusses this concept in more detail:

Implementing a Successful Multiuser Access/JET Application
http://www.accessmvp.com/TWickerath/articles/multiuser.htm

Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

There has GOT to be an easy way to do this and I am beating my head against
the wall. Access 2007....I want my simple database accessable to the other 15

[quoted text clipped - 14 lines]

Thanks all

 

[Tom Wickerath]

Hi Jerry,

SharePoint may be a suitable alternative for you if:

1.) You don't care about Enforced Referential Integrity for the
relationships between your tables and

2.) None of your tables contain lots of records. I've heard that performance
can suffer with the current implementations of Access + SharePoint, with
tables that have more than about 2000 records.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[snackwrap via AccessMonster.com]

Good stuff! And again, thanks Tom. Enforced Referential Integrity is not an
issue as I am working off of only one table. As for size, I will probably
never have more than 150 rows and 20 or so columns. Basically all I am
working on is a simple alternative to manually looking through a hard or soft
copy of a spreadsheet. I took vendor information and dumped it into a combo
box so that from one selection all information can be seen on one page for
anyone in the group.

But I will be reading more into Enforced Referential Integrity as future
databases will have more than one table.

-jerry

Hi Jerry,

SharePoint may be a suitable alternative for you if:

1.) You don't care about Enforced Referential Integrity for the
relationships between your tables and

2.) None of your tables contain lots of records. I've heard that performance
can suffer with the current implementations of Access + SharePoint, with
tables that have more than about 2000 records.

Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

Thanks Tom, a few hours after posting this message I found out that my
organization has a Sharepoint server so I am looking at that option as it

[quoted text clipped - 6 lines]

Thanks again!
-jerry