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

Perhaps not easy, but if you have 2 FEDB's, you can register one of them as
a "library" of the other one.  This will allow you do invoke functions in
the 2nd DB (the "library") from the 1st db.  You can use these functions to
open forms, etc.  I haven't ever done much with this, other than build some
simple function libraries.  You will probably have to have both FEDB's
linked to the tables in the BE.

Note that you cannot, unfortunately, create a circular reference to permit
the 2nd db to invoke functions in the 1st.   I had done this only in A2K, so
just to be sure, I built a Q&D test set in A97 and it seems to work.

Regards,

Steve Goodhall

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


  I have never found an easy way to do this but thanks for asking the
question.

  John W. Colby
  www.colbyconsulting.com

    -----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: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030701/0b28d706/attachment-0001.html>