I searched around a little bit, but didn't come up with the answer to
this question, but somewhere in the back of my mind, I think this can
be done...
Let's say we have two different company functions: Sales and
Operations
The Operations database is considered the "main" one...we are using
this daily and it works very well.
I've now created a new database, which basically tracks prospects and
manages clients and their ongoing projects, which is now considered a
"sales" function.
Because we're having sales followup with clients as well, I'd like the
forms, reports, and code regarding the projects to be exactly the same
in the new sales db as it is in the old db.
Maintenance is a nightmare on all this already.
Is there a way to NOT import, but have the forms, reports, etc. be
exactly the same in both databases (like a reference, I guess), so
that I only need to maintain one of them. In other words, if I make a
change to the form or report or code in the main database, that change
is reflected in the new database.
This can be done, right? I wanna say you do almost like an Add-in
thing, right? How can I get this to work? Any ideas?
Thanks!
Josetta
11  2018 
On 24 Apr 2007 17:40:45 -0700, Josetta <Jo*****@smartd ot.netwrote:
Indeed the term is "add-in". That's where you can put the common
functionality. Both apps would set a reference to this module, and are
then able to use it.
Personally I would rather create a single app, and use security to
fence off certain functionality the user may not need.
-Tom.
>I searched around a little bit, but didn't come up with the answer to
this question, but somewhere in the back of my mind, I think this can
be done...
Let's say we have two different company functions: Sales and
Operations
The Operations database is considered the "main" one...we are using
this daily and it works very well.
I've now created a new database, which basically tracks prospects and
manages clients and their ongoing projects, which is now considered a
"sales" function.
Because we're having sales followup with clients as well, I'd like the
forms, reports, and code regarding the projects to be exactly the same
in the new sales db as it is in the old db.
Maintenance is a nightmare on all this already.
Is there a way to NOT import, but have the forms, reports, etc. be
exactly the same in both databases (like a reference, I guess), so
that I only need to maintain one of them. In other words, if I make a
change to the form or report or code in the main database, that change
is reflected in the new database.
This can be done, right? I wanna say you do almost like an Add-in
thing, right? How can I get this to work? Any ideas?
Thanks!
Josetta
On Apr 24, 5:40 pm, Josetta <Jose...@smartd ot.netwrote:
I searched around a little bit, but didn't come up with the answer to
this question, but somewhere in the back of my mind, I think this can
be done...
Let's say we have two different company functions: Sales and
Operations
The Operations database is considered the "main" one...we are using
this daily and it works very well.
I've now created a new database, which basically tracks prospects and
manages clients and their ongoing projects, which is now considered a
"sales" function.
Because we're having sales followup with clients as well, I'd like the
forms, reports, and code regarding the projects to be exactly the same
in the new sales db as it is in the old db.
Maintenance is a nightmare on all this already.
Is there a way to NOT import, but have the forms, reports, etc. be
exactly the same in both databases (like a reference, I guess), so
that I only need to maintain one of them. In other words, if I make a
change to the form or report or code in the main database, that change
is reflected in the new database.
This can be done, right? I wanna say you do almost like an Add-in
thing, right? How can I get this to work? Any ideas?
Thanks!
Josetta
I do this particular thing all the time. I don't use add-ins for this
particular functionality. Basically, keep the same front-end for all
back-ends and let the user switch backend databases (how you select
the new one is up to you. I use the common file dialog myself
usually), then cycle thru the tabledefs to define the new path to each
linked table. Here is a code snippet (this assumes an Access back-end
database):
For Each tdf In db.TableDefs
' If connect is blank, its not an Linked table
If Len(tdf.Connect ) 0 Then
tdf.Connect = ";DATABASE= " & varFileName
' The RefreshLink might fail if the new path isn't OK. So
trap errors inline.
On Error Resume Next
tdf.RefreshLink
I don't remember off-hand if I wrote that code from scratch or adapted
it from somewhere else (like Getz, Litwin, et. al.). You will
probably need to adapt to your needs, but this should show you the
basic idea.
-- Larry Engles
Access developer since day 1 of Access 1.0
Thanks for the suggestion. The boss would really like to keep them
separate and I am just trying to save myself some work down the road,
since he comes up with these crazy ideas continually. I am going to
look into this add-in business. It looks like this may be the way to
go in the future. For now, I just need to get it done.
Josetta
On Apr 24, 11:35 pm, Tom van Stiphout <no.spam.tom7.. .@cox.netwrote:
On 24 Apr 2007 17:40:45 -0700, Josetta <Jose...@smartd ot.netwrote:
Indeed the term is "add-in". That's where you can put the common
functionality. Both apps would set a reference to this module, and are
then able to use it.
Personally I would rather create a single app, and use security to
fence off certain functionality the user may not need.
-Tom.
I searched around a little bit, but didn't come up with the answer to
this question, but somewhere in the back of my mind, I think this can
be done...
Let's say we have two different company functions: Sales and
Operations
The Operations database is considered the "main" one...we are using
this daily and it works very well.
I've now created a new database, which basically tracks prospects and
manages clients and their ongoing projects, which is now considered a
"sales" function.
Because we're having sales followup with clients as well, I'd like the
forms, reports, and code regarding the projects to be exactly the same
in the new sales db as it is in the old db.
Maintenance is a nightmare on all this already.
Is there a way to NOT import, but have the forms, reports, etc. be
exactly the same in both databases (like a reference, I guess), so
that I only need to maintain one of them. In other words, if I make a
change to the form or report or code in the main database, that change
is reflected in the new database.
This can be done, right? I wanna say you do almost like an Add-in
thing, right? How can I get this to work? Any ideas?
Thanks!
Josetta- Hide quoted text -
- Show quoted text -
Thanks for your reply. Hmm...this works fine with tables and I am
using this to make sure all my tables are linked properly. What I
need is to have this functionality with forms, reports and queries.
On Apr 26, 12:37 am, eng...@ridesoft .com wrote:
On Apr 24, 5:40 pm, Josetta <Jose...@smartd ot.netwrote:
I searched around a little bit, but didn't come up with the answer to
this question, but somewhere in the back of my mind, I think this can
be done...
Let's say we have two different company functions: Sales and
Operations
The Operations database is considered the "main" one...we are using
this daily and it works very well.
I've now created a new database, which basically tracks prospects and
manages clients and their ongoing projects, which is now considered a
"sales" function.
Because we're having sales followup with clients as well, I'd like the
forms, reports, and code regarding the projects to be exactly the same
in the new sales db as it is in the old db.
Maintenance is a nightmare on all this already.
Is there a way to NOT import, but have the forms, reports, etc. be
exactly the same in both databases (like a reference, I guess), so
that I only need to maintain one of them. In other words, if I make a
change to the form or report or code in the main database, that change
is reflected in the new database.
This can be done, right? I wanna say you do almost like an Add-in
thing, right? How can I get this to work? Any ideas?
Thanks!
Josetta
I do this particular thing all the time. I don't use add-ins for this
particular functionality. Basically, keep the same front-end for all
back-ends and let the user switch backend databases (how you select
the new one is up to you. I use the common file dialog myself
usually), then cycle thru the tabledefs to define the new path to each
linked table. Here is a code snippet (this assumes an Access back-end
database):
For Each tdf In db.TableDefs
' If connect is blank, its not an Linked table
If Len(tdf.Connect ) 0 Then
tdf.Connect = ";DATABASE= " & varFileName
' The RefreshLink might fail if the new path isn't OK. So
trap errors inline.
On Error Resume Next
tdf.RefreshLink
I don't remember off-hand if I wrote that code from scratch or adapted
it from somewhere else (like Getz, Litwin, et. al.). You will
probably need to adapt to your needs, but this should show you the
basic idea.
-- Larry Engles
Access developer since day 1 of Access 1.0- Hide quoted text -
- Show quoted text -
On Apr 26, 11:20 am, Josetta <Jose...@smartd ot.netwrote:
Thanks for your reply. Hmm...this works fine with tables and I am
using this to make sure all my tables are linked properly. What I
need is to have this functionality with forms, reports and queries.
On Apr 26, 12:37 am, eng...@ridesoft .com wrote:
On Apr 24, 5:40 pm, Josetta <Jose...@smartd ot.netwrote:
I searched around a little bit, but didn't come up with the answer to
this question, but somewhere in the back of my mind, I think this can
be done...
Let's say we have two different company functions: Sales and
Operations
The Operations database is considered the "main" one...we are using
this daily and it works very well.
I've now created a new database, which basically tracks prospects and
manages clients and their ongoing projects, which is now considered a
"sales" function.
Because we're having sales followup with clients as well, I'd like the
forms, reports, and code regarding the projects to be exactly the same
in the new sales db as it is in the old db.
Maintenance is a nightmare on all this already.
Is there a way to NOT import, but have the forms, reports, etc. be
exactly the same in both databases (like a reference, I guess), so
that I only need to maintain one of them. In other words, if I make a
change to the form or report or code in the main database, that change
is reflected in the new database.
This can be done, right? I wanna say you do almost like an Add-in
thing, right? How can I get this to work? Any ideas?
Thanks!
Josetta
The approach Tom described earlier is the best approach to take, i.e.,
create a single front end database that houses all of the forms,
reports, queries, etc. for both applications and let the end user
either choose which 'application' they want to use (or force them into
one or the other based on their user id or other criteria). Once that
choice is made only make available those forms, reports, queries, etc.
that apply to the chosen application. You can easily share data
between different mdb files, and even code modules, but forms,
queries, and reports are another matter. It's best to keep those in
the same file unless you want the maintenance nightmare you've already
described.
Bruce
On Apr 26, 9:20 am, Josetta <Jose...@smartd ot.netwrote:
Thanks for your reply. Hmm...this works fine with tables and I am
using this to make sure all my tables are linked properly. What I
need is to have this functionality with forms, reports and queries.
On Apr 26, 12:37 am, eng...@ridesoft .com wrote:
On Apr 24, 5:40 pm, Josetta <Jose...@smartd ot.netwrote:
I searched around a little bit, but didn't come up with the answer to
this question, but somewhere in the back of my mind, I think this can
be done...
Let's say we have two different company functions: Sales and
Operations
The Operations database is considered the "main" one...we are using
this daily and it works very well.
I've now created a new database, which basically tracks prospects and
manages clients and their ongoing projects, which is now considered a
"sales" function.
Because we're having sales followup with clients as well, I'd like the
forms, reports, and code regarding the projects to be exactly the same
in the new sales db as it is in the old db.
Maintenance is a nightmare on all this already.
Is there a way to NOT import, but have the forms, reports, etc. be
exactly the same in both databases (like a reference, I guess), so
that I only need to maintain one of them. In other words, if I make a
change to the form or report or code in the main database, that change
is reflected in the new database.
This can be done, right? I wanna say you do almost like an Add-in
thing, right? How can I get this to work? Any ideas?
Thanks!
Josetta
I do this particular thing all the time. I don't use add-ins for this
particular functionality. Basically, keep the same front-end for all
back-ends and let the user switch backend databases (how you select
the new one is up to you. I use the common file dialog myself
usually), then cycle thru the tabledefs to define the new path to each
linked table. Here is a code snippet (this assumes an Access back-end
database):
For Each tdf In db.TableDefs
' If connect is blank, its not an Linked table
If Len(tdf.Connect ) 0 Then
tdf.Connect = ";DATABASE= " & varFileName
' The RefreshLink might fail if the new path isn't OK. So
trap errors inline.
On Error Resume Next
tdf.RefreshLink
I don't remember off-hand if I wrote that code from scratch or adapted
it from somewhere else (like Getz, Litwin, et. al.). You will
probably need to adapt to your needs, but this should show you the
basic idea.
-- Larry Engles
Access developer since day 1 of Access 1.0- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -
I guess I was not detailed enough. The variable "varFileNam e" is
complete path for a backend database. It could be a different
database than is currently linked to. This then would then link to a
different backend. If you feed it the same path and file as the
existing backend, all you are doing is refreshing the link.
Hope this sheds light on the subject. Since the front-end (the mdb
file with the forms, reports, queries, etc.) does not change, you are
using the exact same front-end to re-link to mulitple backends.
-- Larry Engles
Access developer since day 1 of Access 1.0
Josetta <Jo*****@smartd ot.netwrote in news:1177461645 .121679.261130
@b40g2000prd.go oglegroups.com:
Is there a way to NOT import, but have the forms, reports, etc. be
exactly the same in both databases (like a reference, I guess), so
that I only need to maintain one of them. In other words, if I make a
change to the form or report or code in the main database, that change
is reflected in the new database.
This can be done, right?
It could be done quite easily in Access 97 using the VB Attributes of the
objects. But it became more difficult in Access 2000. I wrote code to
accomplish this long ago but who knows where it might be now?
If you search Google Groups comp.databases. ms-access for ATTRIBUTE
VB_Exposed you should be able to find some interesting suggestions. Terry
Kreft may be the person most knowledgable about this matter.
Also, you might want to remember that old style MS-VB Forms !!!!MAY!!!! be
possible in modern versions of Access, although this is unlikely to help
with reports.
On 26 Apr 2007 09:15:16 -0700, Josetta <Jo*****@smartd ot.netwrote:
One other way to simulate two apps with one is to borrow a trick from
the UNIX command line days. They would have utilities that were
several-in-one, and depending on the name they would behave
differently.
You can do a similar thing. Create a shortcut like this:
<path_to>msacce ss.exe <path_to>my.m db /x:AppOne
and another one:
<path_to>msacce ss.exe <path_to>my.m db /x:AppTwo
Then in the macro named AppOne you have:
RunCode Initialize("App One")
and in a macro named AppTwo you have:
RunCode Initialize("App Two")
The public function Initialize in a standard module would configure
the app. Perhaps:
Public Function Initialize(ByVa l strMode as String)
if strMode = "AppOne" then
DoCmd OpenForm "MainMenuForApp One"
elseif strMode = "AppTwo" then
DoCmd OpenForm "MainMenuForApp Two"
else
Msgbox "You can only run this app from an approved shortcut"
End
end if
-Tom.
>Thanks for the suggestion. The boss would really like to keep them
separate and I am just trying to save myself some work down the road,
since he comes up with these crazy ideas continually. I am going to
look into this add-in business. It looks like this may be the way to
go in the future. For now, I just need to get it done.
Josetta
On Apr 24, 11:35 pm, Tom van Stiphout <no.spam.tom7.. .@cox.netwrote:
>On 24 Apr 2007 17:40:45 -0700, Josetta <Jose...@smartd ot.netwrote:
Indeed the term is "add-in". That's where you can put the common
functionalit y. Both apps would set a reference to this module, and are
then able to use it.
Personally I would rather create a single app, and use security to
fence off certain functionality the user may not need.
-Tom.
>I searched around a little bit, but didn't come up with the answer to
this question, but somewhere in the back of my mind, I think this can
be done...
>Let's say we have two different company functions: Sales and
Operations
>The Operations database is considered the "main" one...we are using
this daily and it works very well.
>I've now created a new database, which basically tracks prospects and
manages clients and their ongoing projects, which is now considered a
"sales" function.
>Because we're having sales followup with clients as well, I'd like the
forms, reports, and code regarding the projects to be exactly the same
in the new sales db as it is in the old db.
>Maintenance is a nightmare on all this already.
>Is there a way to NOT import, but have the forms, reports, etc. be
exactly the same in both databases (like a reference, I guess), so
that I only need to maintain one of them. In other words, if I make a
change to the form or report or code in the main database, that change
is reflected in the new database.
>This can be done, right? I wanna say you do almost like an Add-in
thing, right? How can I get this to work? Any ideas?
>Thanks!
>Josetta- Hide quoted text -
- Show quoted text -
Yes, I am finding this out. What I wanted to avoid was making changes
in both places... Thanks for your suggestion. I'm going to seriously
think about it.
On Apr 26, 4:19 pm, Bruce <deluxeinformat ...@gmail.comwr ote:
On Apr 26, 11:20 am, Josetta <Jose...@smartd ot.netwrote:
Thanks for your reply. Hmm...this works fine with tables and I am
using this to make sure all my tables are linked properly. What I
need is to have this functionality with forms, reports and queries.
On Apr 26, 12:37 am, eng...@ridesoft .com wrote:
On Apr 24, 5:40 pm, Josetta <Jose...@smartd ot.netwrote:
I searched around a little bit, but didn't come up with the answer to
this question, but somewhere in the back of my mind, I think this can
be done...
Let's say we have two different company functions: Sales and
Operations
The Operations database is considered the "main" one...we are using
this daily and it works very well.
I've now created a new database, which basically tracks prospects and
manages clients and their ongoing projects, which is now considered a
"sales" function.
Because we're having sales followup with clients as well, I'd like the
forms, reports, and code regarding the projects to be exactly the same
in the new sales db as it is in the old db.
Maintenance is a nightmare on all this already.
Is there a way to NOT import, but have the forms, reports, etc. be
exactly the same in both databases (like a reference, I guess), so
that I only need to maintain one of them. In other words, if I make a
change to the form or report or code in the main database, that change
is reflected in the new database.
This can be done, right? I wanna say you do almost like an Add-in
thing, right? How can I get this to work? Any ideas?
Thanks!
Josetta
The approach Tom described earlier is the best approach to take, i.e.,
create a single front end database that houses all of the forms,
reports, queries, etc. for both applications and let the end user
either choose which 'application' they want to use (or force them into
one or the other based on their user id or other criteria). Once that
choice is made only make available those forms, reports, queries, etc.
that apply to the chosen application. You can easily share data
between different mdb files, and even code modules, but forms,
queries, and reports are another matter. It's best to keep those in
the same file unless you want the maintenance nightmare you've already
described.
Bruce- Hide quoted text -
- Show quoted text -
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Matt Alanzo |
last post by:
On another newsgroup an Access knowledgable party posted:
>You should be able to connect an Access ADP to an existing SQLExpress
>database running in SQLS 2000 compatibility mode. The only thing you
>won't be able to do is access any of the design surfaces for SQLS
>objects in the ADP. I checked with the Access team on this :-)
>
I appealed for clarification but without reply. Maybe somone on this
newsgroup can provide insight.
|
by: Grasshopper |
last post by:
Hi,
I am automating Access reports to PDF using PDF Writer 6.0. I've
created a DTS package to run the reports and schedule a job to run this
DTS package. If I PC Anywhere into the server on where the job is
running, the job runs sucessfully, PDF files got generated, everything
is good. If I scheduled the job to run at the time that I am not
logged into the server, Access is not able to print to the printer.
The error is pretty...
|
by: Ashura |
last post by:
H
I want to make a project where one or more object could be shared between 2 applications
For example : the first application create a connection to a web-service, this connection is stored in an object (through a service perhaps). A second application is launch and I want this application, use the same connection as the frst one (so retrieve the object where the connection is stored)
Any idee of th process ??
I think I need to...
|
by: James |
last post by:
I have a VB windows forms application that accesses a Microsoft Access
database that has been secured using user-level security. The
application is being deployed using No-Touch deployment. The objective
in utilizing this new deployment method is to reduce the maintenance
overhead as well as making it easier for my users to setup and run the
application initially. I have VS 2002, Windows XP, Access XP(2000
format).
He is my problem....
|
by: Bob |
last post by:
How do I program vb.net to copy a query or table from one MS Access database
to another?
I'd like to accomplish what import does when it copies Access objects
(primarily queries but some tables) from another database into the database
where the import action is selected---EXCEPT that I'd like to do this
externally with a VB.net program.
--
Thanks, Bob
| | |
by: Lüpher Cypher |
last post by:
Hi,
Suppose we have a hierarchical class structure that looks something like
this:
Object
|
+-- Main
|
+-- Object1
|
by: Jeff User |
last post by:
Hi
I want to create a rather simple object with a few string attributes
to hold some database user information such as:
public class UserInfo
{
//Basic user information for each user associated with a database.
private string sDbName;
private string sUserName;
.... other stuff....
|
by: garyusenet |
last post by:
I could do with something similiar, can you tell me if you think this
would work for me, and if there's any advantage in working with
controls
this way than how I currently am.
At the moment i'm using the treenodes and each treenode needs a unique
entry into my rich text box. After sitting at home with MSDN i've
managed to get this functionality by storing a RTF string in the tag
property of the treenode. On every 'before update' of the...
|
by: Robert |
last post by:
How do you get an accurate count of the number of records returned from
a query when using linked tables.
I have an access 2003 database as a front end to another access 2003
database that contains only tables. I have linked the tables for the
front end to the back end database.
I am trying to set the recordsource of a form to a query established by
the user to narrow the scope but I don't want to display the form if
there are no...
|
by: Jer |
last post by:
I just upgraded to SQLServer 2005 Standard. I do development in a
database on one server. When a solution is completely tested, I move
it to the operational database on a different server. With SQLServer
2000, I could just open the .adp file and do File->Get External
Data->Import to move the objects. That does not work with 2005.
What is the recommended method for moving objects from one database to
another? Obviously, the objects...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
| | |
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth.
The Art of Business Website Design
Your website is...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
| | |
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols.
I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
|
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...
| |
