Single Front End File with Form that Can by Filtered By User

[Desilu via AccessMonster.com]

I’ve got an Expense Report DB that I split into a back-end (tables) and
multiple front-ends (for my users). I understand why one needs to split the
DB, however because I’ve tailored the switchboard and some other forms to the
users (using filters, etc) I now realize I’ve created a maintenance nightmare.


These users will not be creating any forms, reports, macros or functions.
They will simply be adding or possibly deleting records from the tables via
their forms. From what I've experienced, a FE doesn't lock multiple users
out if they are only running queries or populating tables. Therefore, now I
am thinking what I should have done was create one user FE with a menu that
takes the user to a form that is filtered, based on their click-event
password. This way I can maintain one front-end, vs. trying to keep up with
the multiple versions out there. (There are multiple versions because of the
forms being created multiple times with user defined filters.)

I’ve always had trouble with creating one form with updatable filters. I end
up creating multiple versions of the form and embedding the filter, etc. (one
form per user)

Can I create one form in one front-end that is shared (as mentioned above)
with filters by user? I don’t want anyone to be able to unfilter.

Thanks.

 

[Klatuu]

I don't know what you mean by an fe doesn't lock multiple users out. Why
would you need them to? Why do your forms need to be user specific?

It is normal and usual for users to each have an fe all linked to one be.

 

[Desilu via AccessMonster.com]

I don't know what you mean by an fe doesn't lock multiple users out. Why
would you need them to? Why do your forms need to be user specific?

It is normal and usual for users to each have an fe all linked to one be.

I’ve got an Expense Report DB that I split into a back-end (tables) and
multiple front-ends (for my users). I understand why one needs to split the

[quoted text clipped - 19 lines]

Thanks.

I've found that multiple people can use one FE, as long as they are not
creating or editing forms, macros, reports, functions. That's our typical
user where I work. If I try to create a form or edit one, while you are in
the same FE running a query (or whatever) I'll get an error message saying I
don't have exclusive access or rights to the DB.

My forms are only specific so I can handle the filtering. Therefore, they
only see their expenses in any form view/query, etc. Do you know if one
form can be created, where user filters can be applied and not removed to see
all records?

 

[Klatuu]

There are multiple ways to do this. How are you doing your filtering?

NEVER EVER have multiple users sharing the same front end.

One example is to apply filtering based on who the user is. Are you using
workgroup security?
--
Dave Hargis, Microsoft Access MVP

I don't know what you mean by an fe doesn't lock multiple users out. Why
would you need them to? Why do your forms need to be user specific?

It is normal and usual for users to each have an fe all linked to one be.

I’ve got an Expense Report DB that I split into a back-end (tables) and
multiple front-ends (for my users). I understand why one needs to split the

[quoted text clipped - 19 lines]

Thanks.

I've found that multiple people can use one FE, as long as they are not
creating or editing forms, macros, reports, functions. That's our typical
user where I work. If I try to create a form or edit one, while you are in
the same FE running a query (or whatever) I'll get an error message saying I
don't have exclusive access or rights to the DB.

My forms are only specific so I can handle the filtering. Therefore, they
only see their expenses in any form view/query, etc. Do you know if one
form can be created, where user filters can be applied and not removed to see
all records?

 

[Desilu via AccessMonster.com]

There are multiple ways to do this. How are you doing your filtering?

NEVER EVER have multiple users sharing the same front end.

One example is to apply filtering based on who the user is. Are you using
workgroup security?[quoted text clipped - 16 lines]

form can be created, where user filters can be applied and not removed to see
all records?

I'm filtering by using a user table that I created that links my user to the
expenses via sql, etc. It's an sql statement that's the record source behind
the form, vs. saving a query and basing the form on the query.

I haven't used workgroup security. I'm not sure I understand it. Seems what
I've read it leads me to believe it's difficult to set up or that it can be
fickel.

In the example that users are only interacting with tables or queries, why
can't they share one front-end? Is it about possible damage? I can see
reasons to have multiple front-ends, but I'm not sure I understand why it's
necessary in this example.

 

[Pat Hartman]

Go back to a single FE (which will be distributed to all users so they have
their own copy) with a single instance of each form. There are a number of
methods to use to control what shows on a form and the best method will
depend on how your application works. I'll give you one scenario that I use
most often.

Use the Where argument of the OpenForm method to supply criteria for
limiting the form. this is easier to manage than filters and more efficient
when working with SQL server databases. It doesn't impact the efficiency of
a Jet BE database but is good practice never the less.

If your users log in, you ca capture their ID's and use them as the criteria
to select data for a particular user.

Lookup OpenForm in help for details or you can rely on intellisense to guide
you as you are typing in the VBA window.

 

[Desilu via AccessMonster.com]

Go back to a single FE (which will be distributed to all users so they have
their own copy) with a single instance of each form. There are a number of
methods to use to control what shows on a form and the best method will
depend on how your application works. I'll give you one scenario that I use
most often.

Use the Where argument of the OpenForm method to supply criteria for
limiting the form. this is easier to manage than filters and more efficient
when working with SQL server databases. It doesn't impact the efficiency of
a Jet BE database but is good practice never the less.

If your users log in, you ca capture their ID's and use them as the criteria
to select data for a particular user.

Lookup OpenForm in help for details or you can rely on intellisense to guide
you as you are typing in the VBA window.

I've got an Expense Report DB that I split into a back-end (tables) and
multiple front-ends (for my users). I understand why one needs to split

[quoted text clipped - 29 lines]

Thanks.

The method you are suggesting, can it be unfiltered by using a short-cut menu
or any menu? I'm thinking it can't and works sort of like my sql did when I
linked my user table to the expenses.

 

[Pat Hartman]

The "filtering" is external and is applied as the form is opened therefore,
you can open the form without the filtering or with it. If you want to
handle this programmatically, test the contents of the criteria field on the
form and if it is null, open without filtering and if there is a value, open
with the where clause.

Go back to a single FE (which will be distributed to all users so they
have
their own copy) with a single instance of each form. There are a number
of
methods to use to control what shows on a form and the best method will
depend on how your application works. I'll give you one scenario that I
use
most often.

Use the Where argument of the OpenForm method to supply criteria for
limiting the form. this is easier to manage than filters and more
efficient
when working with SQL server databases. It doesn't impact the efficiency
of
a Jet BE database but is good practice never the less.

If your users log in, you ca capture their ID's and use them as the
criteria
to select data for a particular user.

Lookup OpenForm in help for details or you can rely on intellisense to
guide
you as you are typing in the VBA window.

I've got an Expense Report DB that I split into a back-end (tables) and
multiple front-ends (for my users). I understand why one needs to split

[quoted text clipped - 29 lines]

Thanks.

The method you are suggesting, can it be unfiltered by using a short-cut
menu
or any menu? I'm thinking it can't and works sort of like my sql did when
I
linked my user table to the expenses.