Using Acces 2003.
Different FE's: The client will be the main user of the small database
capturing sales information. He wants his sales guys to also have a copy of
the database, but essentially a 'cut down' version which will not show all
the same fields on some of the forms but will allow them to enter the data
to update the database.
1. Each salesguy should only be able to pull up his own sales data only.
2. The database although small will be split FE/BE
Q1: Do I need to create different forms for the sales guys and the main
client and alter the FE settings when installing? Is this the hard way of
doing things?
REPLICATION:
Knowing the above, when the sales guys updates their own data. How does
replicaiton work in regards to having new information entered and existing
data updated, update the main users copy?
Q2: Do I need to have the main user have a 'replicated' copy as well?
Thanks in advance.
Michelle
** Please only reply to the newsgroup **
There are 2 questions here:
A. split functionality for different users.
You can use the exact same FE for all users without tweeking at
install:
1. Create a staff table with user IDs, names passwords etc. and decide
on different fields which describe what category of user they are and
maybe some fields representing yes/no things they can/ can't do.
2. On login launch a form which takes a user name and checks the
password
3. In a temporary front end table if the login is correct put in the
user ID, login time, whatever other info you want to record.
4. Dynamically in the code of the database, you can select different
forms depending on the rights associated with the user ID - and within
the forms even allow/ prevent options being used. For example:
function ctrlButton_click()
Dim User as Integer
User = dlookup("[UserID]","[tblUserTmp]")
if dlookup("[CanAddRecords]","[tblStaff]","[UserID] = " & User) = -1
then
docmd.openform "frmReadWriteForm"
Else
docmd.openform "frmReadOnlyForm
end if
end function
or in the form load function of a form you could put something similar:
Dim User as Integer
User = dlookup("[UserID]","[tblUserTmp]")
if dlookup("[CanViewFinance]","[tblStaff]","[UserID] = " & User) = -1
then
me.txtFinance.visible = true
Else
me.txtFinance.visible = false
endif
This isnt exactly iron clad security or anything close to it, but it is
useful to seperate user functionality. If your feeling brave you can
tie it in to the access user groups for a bit of real (ish) security.
B. How does replication work?
There is a lot written on this topic by people who know more than me -
(check out microcoft.public.access.replication) but a basic overview is
this:
When you create the backend you replicate it using the wizard and place
the "design master" of it on the server. Place a replica backend then
on each pc. when a pc is networked, the information on the design
master and the local backend can be synchronised so that changes are
updated across the two and they then hold the same data after
synchronisation. when on the road, users use the local backend and when
they are at the office they synchronise the data and use the network
backend.
There are a lot of issues about conflicting updates, deletes, and
possible corruptions and their resolutions. It's not impossible - but
it's not easy either and its worth researching before you jump into it.
Hope this helps
Michelle - 16 Jan 2006 23:28 GMT
Thank you so much for your time in giving that information. I will look
further into what you have written in order to better understand it.
I may post again at a later date under the same heading if I have further
question
Thanks again
Michelle
> There are 2 questions here:
>
[quoted text clipped - 57 lines]
>
> Hope this helps