question 2 on security

[joe]

I want to split my DB using front end/back end design...forms and reports on users desktops,,tables in server.The itd group has stated only a limited amount of space is reserved per department on the server.This DB is used to track credit requests and without the three people being joined to the same tables to run reports and run queries, the purpose would end up useless in tracking all these requests.Are there any options to this scenario or have i hit the wall with this idea and i am at the mercy of the itd group?thanks for the shoulder to cry on,,,,,,,,

 

[Joan Wild]

How big is the backend? I can't imagine that the backend would be that
large with three people tracking credit requests.

You could perhaps enlist the three people in your approach to IT. Their
jobs will be affected without the database, right?

Also ensure that you routinely compact the backend. Since you are posting
in the security group, and have already asked some questions about security,
you should know that you shouldn't run the splitter wizard on a secure
database. That will result in a secure frontend and unsecure backend.
Follow the steps at
http://www.jmwild.com/SplitSecure.htm

--
Joan Wild
Microsoft Access MVP

I want to split my DB using front end/back end design...forms and reports

on users desktops,,tables in server.The itd group has stated only a limited
amount of space is reserved per department on the server.This DB is used to
track credit requests and without the three people being joined to the same
tables to run reports and run queries, the purpose would end up useless in
tracking all these requests.Are there any options to this scenario or have i
hit the wall with this idea and i am at the mercy of the itd group?thanks
for the shoulder to cry on,,,,,,,,

 

[joe]

Thanks for the informative website..i will follow it.In regards to server space and compacting? How much does compacting really do? The transactions would be the equivalent of about 150 transactions daily with five fields used.With time, it will get large so is there an option to 'dump' or backup data from the tables, burn em on cd then remove all data to start again?This idea may extend to others in the department since they handle different requests and it is a major change of how work is done.Thanks for all your help

 

[Joan Wild]

Compacting should be done routinely on any database. I would suggest
weekly.

150 transactions a day is not that much, so it will be with a long, long
time that it will get large. I don't see any need to archive the data and
start over; however backup should be done daily ;-).

You can schedule the compacting to occur a night when no one is in the
database - it really isn't that big a deal.

--
Joan Wild
Microsoft Access MVP

Thanks for the informative website..i will follow it.In regards to server

space and compacting? How much does compacting really do? The transactions
would be the equivalent of about 150 transactions daily with five fields
used.With time, it will get large so is there an option to 'dump' or backup
data from the tables, burn em on cd then remove all data to start again?This
idea may extend to others in the department since they handle different
requests and it is a major change of how work is done.Thanks for all your
help

 

[Ami Dalwadi]

Hi, Joe

You Need To DO Set Up Your Start Up Option And Then
You Need To Work Around Rights

1. FIRST KEEP 1 OR 2 SPERATE COPY OF YOUR MDB FILE/
CODE BEFORE YOU DO THIS STESS, SO IF YOU GET LOST THEN
YOU CAN RECOVER WITH THIS EXTRA COPIES

NOW HERE IS STEPS
******************
(I guess You Know How To Create User, Group In Ms
Access 2002)


Create Group Call : ReportUser
Assign Following Right To This GROUP(NOT USERS) On
Following Objects :

DataBase : OPEN /RUN ONLY
Table : Read Design, Read Data
Query : Read Design, Read Data
Form :Open Run, Read Design
Report : Open Run, Read Design

Then Create 2 USER For Your Report

Add User to Above ReportUser Group

REVOKE ALL PERMISSION FROM EACH INDIVIDUAL USER,
BECAUSE WE HAVE ASSIGN PERMISSION TO GROUP LEVEL

SO, THEY CAN ONLY RUN FORM AND REPORTS.

TO PREVENT THEM CHANGING TOOL BAR, YOU NEED TO
CUSTOMIZE YOUR START OPTIONS AS FOLLOWS :

GO TO TOOLS---> START UP

DO FOLLOWING SET UP :

ALLOW TOOLBAR/MENU CAHNGES : FALSE(REMOVE TICK), THEY
CAN'T CHANGE/CUSTOMISE YOUR MENU OR TOOL BAR ON FORM,
REPORT

ALLOW DEFAULT SHORT CUT MENUS : FALSE(REMOVE TICK),SO
THEY CAN'T USE ANY SHORT CUT MENUS

DISPLAY DATABASE WINDOW : FALSE(REMOVE TICK), SO THEY
CAN'T SEE YOUR LIST OF FROM,TALBE REPORT ETC

PRESS OK AND CLOSE PROJECT

THEN TEST THIS OPTIONS......


BUT AFTER THIS YOU NEED TO WRITE CODE TO CUSTOMISE
MENU BAR AND TOOL BAR BASED ON CURRENT USER LOG ON


FOR THAT YOU NEED FOLLOWING LOGIC

1.GRAB CURRENT USER BASED ON HIS LOGIN

2.CHECK IF HE IS ADMIN THEN GIVE FULL MENU BAR AND
TOOL BAR OPTIONS

3.IF HE IS NOT ADMIN AND IF HE IS REPORT USER THEN
DISABLE CERTAIN OPTION FROM MENU BAR ANND TOOL BAR

FOR EXAMPLE ON MENU BAR :
FILE---> SAVE, FILE---EXPORT

ON TOOL BAR :
HIDE VIEW,REFRESH,...ETC OPTIONS


TO DO ALL THIS

MAKE ALL SAMPLE MDB FILE AND RUN ALL THIS TEST, THEN
PUT TO GETHER.

I HOPE THIS WILL GIVE YOU LOT OF IDEA HOW YOU SOLVE
YOUR PROBLEM....

AMI

-----Original Message-----
I want to split my DB using front end/back end

design...forms and reports on users desktops,,tables in
server.The itd group has stated only a limited amount of
space is reserved per department on the server.This DB is
used to track credit requests and without the three
people being joined to the same tables to run reports and
run queries, the purpose would end up useless in tracking
all these requests.Are there any options to this scenario
or have i hit the wall with this idea and i am at the
mercy of the itd group?thanks for the shoulder to cry
on,,,,,,,,