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

rusty.hammond at cpiqpc.com rusty.hammond at cpiqpc.com
Wed Jul 2 15:15:50 CDT 2003


Barbara,
 
I've sent you two mdb files with the code and some sample objects offline.
 
Rusty
 
-----Original Message-----
From: Barbara Ryan [mailto:BarbaraRyan at cox.net]
Sent: Tuesday, July 01, 2003 2:23 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Two front end databases with one user interface?


Rusty.... This sounds like something that would work really well for me.  I
would love to have a sample of the code...........Thanks, Barb

----- Original Message ----- 
From: rusty.hammond at cpiqpc.com <mailto:rusty.hammond at cpiqpc.com>  
To: accessd at databaseadvisors.com <mailto:accessd at databaseadvisors.com>  
Sent: Tuesday, July 01, 2003 2:46 PM
Subject: RE: [AccessD] Two front end databases with one user interface?

I've never done it but how about something like this:
 
Put some functionality in the vanilla version that checks for the existence
of a custom.mdb in the same directory as the vanilla front end.  If it's
there, then open it and import the custom objects into the working
interface.  You could have a Custom options  menu item on your main menu
that would open another menu that would drive your Custom options.  This
Custom options menu would exist in the custom.mdb and be imported with the
other custom objects.  If you will be importing objects from the custom.mdb
that have the same names as objects in your vanilla front end, your code
will need to delete the object in the vanilla front end before importing the
custom object.
 
If you are running the front end on the local hard drive, you could copy the
custom.mdb to their hard drive as well.  Then you are only modifying the
copy of the front end.  The master copy of the vanilla front end remains
untouched.  Any additional customizations are added to the custom.mdb which
is then copied down to the local hard drive.
 
 You would need code to:
A. Search for the existence of custom.mdb in the same directory as your
running front end
B. Spin through the list of objects in the custom.mdb and compare the names
to the list of objects in the vanilla front end AND if any match, delete
them in the vanilla front end.
C. Import the objects from the custom.mdb
 
I've already setup a test.mdb and a custom.mdb and will be working on the
code to do this so if you need a sample let me know and I'll try to have
something for you soon.
 
HTH
 
Rusty
 
 -----Original Message-----
From: John Colby [mailto:jcolby at colbyconsulting.com]
Sent: Tuesday, July 01, 2003 12: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



  _____  




_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030702/dd0d1e68/attachment-0001.html>


More information about the AccessD mailing list