|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
I would like to put the backend of an Access 2000 in a folder on the server.
This folder is not open for general use. But I need to put one of the forms
from the database out for public viewing data entry. What functions within
Access could I use. Any help is appreciated.
Thanks.
|
|
Donna,
You can use the database splitter option, or you can do it manually.
Pre-Option:
within Access, click Tools>Database Utilities>Database Splitter
It will then ask you to split the database, click "Split database"
It will now ask you where you want to place the Back-End Database, this is
the file that you are going to want to leave on your secured folder on the
network.
After the database split is complete, you will see that there are two
files for your database, one that is
"Your database name.mdb" and "Your database name_be.mdb"
the file with "_be" should be left on the server, and the other one can be
distributed among users.
**NOTE: any user on the database will need 'read' rights to the secured
folder on the network**
if you need any other help, please reply!! good luck and have a great day!!
Donna wrote:
[Quoted Text] >I would like to put the backend of an Access 2000 in a folder on the server.
>This folder is not open for general use. But I need to put one of the forms
>from the database out for public viewing data entry. What functions within
>Access could I use. Any help is appreciated.
>
>Thanks.
--
KMJ >!
Message posted via http://www.accessmonster.com
|
|
Thank you for the help. I am beginning to see how this database must be
setup. Public users of the db should be able to see just one form in the db,
not the tables, queries, etc. Any input to the form must be able to update
the tables.
Would I still use the split function or should I be looking at security
access, etc?
Once again, thanks!
"krzysztof via AccessMonster.com" wrote:
[Quoted Text] > Donna, > > You can use the database splitter option, or you can do it manually. > > Pre-Option: > within Access, click Tools>Database Utilities>Database Splitter > > It will then ask you to split the database, click "Split database" > > It will now ask you where you want to place the Back-End Database, this is > the file that you are going to want to leave on your secured folder on the > network. > > After the database split is complete, you will see that there are two > files for your database, one that is > "Your database name.mdb" and "Your database name_be.mdb" > > the file with "_be" should be left on the server, and the other one can be > distributed among users. > > **NOTE: any user on the database will need 'read' rights to the secured > folder on the network** > > if you need any other help, please reply!! good luck and have a great day!! > > > > > Donna wrote: > >I would like to put the backend of an Access 2000 in a folder on the server. > >This folder is not open for general use. But I need to put one of the forms > >from the database out for public viewing data entry. What functions within > >Access could I use. Any help is appreciated. > > > >Thanks. > > -- > KMJ >! > > Message posted via http://www.accessmonster.com> > |
|
you can create a user-level security for your access db. it ranks about an 8
out of 10 in toughness if it is your first time doing it, but it pays off.
run the database user-level security wizard - its pretty decent. also, use
the Tools>Start up option, and click off the 'Display Database window' and
that will hide the database window at startup for the users. that way they
wont see everything. but dont worry, you can get it back by clicking, Window
[Quoted Text] > unhide, or hold the shift key when you open the db. it isnt the most
secure thing you can do, but it will deter most users. as for seeing certain
data for certai n users, it can be done in the wizrd, but i suggest maybe a
quick tutorial or manual for your first time. unfortunately it is too long to
explain here!!
Donna wrote:
>Thank you for the help. I am beginning to see how this database must be
>setup. Public users of the db should be able to see just one form in the db,
>not the tables, queries, etc. Any input to the form must be able to update
>the tables.
>Would I still use the split function or should I be looking at security
>access, etc?
>Once again, thanks!
>
>> Donna,
>>
>[quoted text clipped - 29 lines]
>> >
>> >Thanks.
--
KMJ >!
Message posted via http://www.accessmonster.com
|
|
Once again, thanks.
The users know about holding down the shift key or "unhiding" the database.
It looks like I will have to take the dive and set up security measures. Can
you point me in the right direction for a tutorial or "step-by-step"
directions?
"krzysztof via AccessMonster.com" wrote:
[Quoted Text] > you can create a user-level security for your access db. it ranks about an 8 > out of 10 in toughness if it is your first time doing it, but it pays off. > run the database user-level security wizard - its pretty decent. also, use > the Tools>Start up option, and click off the 'Display Database window' and > that will hide the database window at startup for the users. that way they > wont see everything. but dont worry, you can get it back by clicking, Window > > unhide, or hold the shift key when you open the db. it isnt the most > secure thing you can do, but it will deter most users. as for seeing certain > data for certai n users, it can be done in the wizrd, but i suggest maybe a > quick tutorial or manual for your first time. unfortunately it is too long to > explain here!! > > Donna wrote: > >Thank you for the help. I am beginning to see how this database must be > >setup. Public users of the db should be able to see just one form in the db, > >not the tables, queries, etc. Any input to the form must be able to update > >the tables. > >Would I still use the split function or should I be looking at security > >access, etc? > >Once again, thanks! > > > >> Donna, > >> > >[quoted text clipped - 29 lines] > >> > > >> >Thanks. > > -- > KMJ >! > > Message posted via http://www.accessmonster.com> > |
|
|