[AccessD] Two front end databases with one user interface?

Wortz, Charles CWortz at tea.state.tx.us
Tue Jul 1 13:31:41 CDT 2003


Barb,

If you are using Access User-Level Security you can set things up so
those that are members of group A will see the objects for group A while
those in group B will see the objects for group B and neither need know
about the other.


Charles Wortz 
Software Development Division 
Texas Education Agency 
1701 N. Congress Ave 
Austin, TX 78701-1494 
512-463-9493 
CWortz at tea.state.tx.us 
-----Original Message-----
From: John Bartow [mailto:john at winhaven.net] 
Sent: Tuesday 2003 Jul 01 13:23
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Two front end databases with one user interface?

Barb,
You could do that but instead of presenting a different form in the FE
for that user open a different form in another FE. I did that with one
of the apps until it was fully integrated into the main FE.

Of course this was the entire app. If you're opening one specific form
and there is more than just that one form in the other FE then you'de
have to work something out for that. Maybe put each special form in its
own FE? (Thats just a wild swing at a solution, could get ugly.)

Select Case gintDeptID
Case "PITA depart."
    Dim strStAppName As String
    strStAppName = "C:\Program Files\Access 97 Runtime\Msaccess.exe
""N:\PITAForm1.mde"""
    Call Shell(strStAppName, 1)
Case Else
    "open the vanilla form"
End Select

JB
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Barbara Ryan
Sent: Tuesday, July 01, 2003 1:08 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Two front end databases with one user interface?


Thanks, John......

I was hoping to limit the number of objects in my "vanilla" front end by
keeping the "really specific" customizations in another FE.  

This is funny--- I didn't quite catch on to the acronym "PITA" --- I
thought it must be some high-tech thing, so I did a search in Google.
Found the "Palestine Information Technology Association", the "Pacific
Islands Telecommunications Association", the Pacific International
Trapshooting Association....

...but it just clicked --- that it's a Pain......

Barb
----- Original Message ----- 
From: John Bartow 
To: Access Developers discussion and problem solving 
Sent: Tuesday, July 01, 2003 1:27 PM
Subject: RE: [AccessD] Two front end databases with one user interface?


I do something kind of similar with an app. Its a PITA!

It entails using a login (which I have happen automatically based on the
windows login if it matches the staff table info). I then hold info in
variables about about what the person can see and if necessary how they
see it.

So for instance if the forms a person is allowed to see, based the
department they work for and their "security" (my built in security-not
access's) then they just don't get the icons for the other forms
displayed. When there is a choice of forms to use for the same info they
get "their" version of the form. How the position their forms is called
everytime a form opens and reset to the postion when it closes. 

I store some of this info (personal choices for UI settings) in the
registry and other info (such as security-which is required in case they
login into someone elses PC) in the "staff" table.

BTW did I mention that its a PITA?

I suppose you could get it set up in a class framework but I haven't
gone there yet.
HTH
JB

PS: did I mention that its a PITA?
:o)
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Barbara Ryan
Sent: Tuesday, July 01, 2003 12:04 PM
To: Access List
Subject: [AccessD] Two front end databases with one user interface?


I have a "vanilla" Access 97 application that is used at multiple sites.
If a particular site want a modification --- e.g., a customized version
that I do NOT want to incorporate into the vanilla version, is there a
way that I can create a separate front end (to hold these custom
objects) yet still have one user interface?  I don't want them to have
to open two separate applications.

Hope this makes sense!

Thanks,
Barb Ryan


More information about the AccessD mailing list