By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,572 Members | 959 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,572 IT Pros & Developers. It's quick & easy.

link to form in other db

P: n/a
Hi,

Is it (in Access2003) possible yo link from a form in db1 to a form in db2?

Thanks,

Susan
Oct 31 '08 #1
Share this Question
Share on Google+
10 Replies


P: n/a
"susan" <vd*@hotmail.comwrote in message
news:bb***************************@cache5.tilbu1.n b.home.nl...
Hi,

Is it (in Access2003) possible yo link from a form in db1 to a form in
db2?
You can link tables, is that what you mean? What is it you're trying to
achieve?

Keith.
www.keithwilby.co.uk

Oct 31 '08 #2

P: n/a

"Keith Wilby" <he**@there.comschreef in bericht
news:49**********@glkas0286.greenlnk.net...
"susan" <vd*@hotmail.comwrote in message
news:bb***************************@cache5.tilbu1.n b.home.nl...
>Hi,

Is it (in Access2003) possible yo link from a form in db1 to a form in
db2?

You can link tables, is that what you mean? What is it you're trying to
achieve?

Keith.
www.keithwilby.co.uk
db1 is a MDE. I distributed this to several users. There are users who want
to have extra options. I want to give them this possibility to let them
build themselves these extensions. Yherefor I want to create a commandbutton
"Extra" in db1 which links to a Form "MyExtras"in db2. From this form the
user can build his own extra functionality.
Oct 31 '08 #3

P: n/a
"susan" <vd*@hotmail.comwrote in message
news:66***************************@cache1.tilbu1.n b.home.nl...
>
"Keith Wilby" <he**@there.comschreef in bericht
news:49**********@glkas0286.greenlnk.net...
>"susan" <vd*@hotmail.comwrote in message
news:bb***************************@cache5.tilbu1. nb.home.nl...
>>Hi,

Is it (in Access2003) possible yo link from a form in db1 to a form in
db2?

You can link tables, is that what you mean? What is it you're trying to
achieve?

Keith.
www.keithwilby.co.uk

db1 is a MDE. I distributed this to several users. There are users who
want to have extra options. I want to give them this possibility to let
them build themselves these extensions. Yherefor I want to create a
commandbutton "Extra" in db1 which links to a Form "MyExtras"in db2. From
this form the user can build his own extra functionality.
You can't make design changes to forms in an MDE. The scenario you describe
is an unorthadox one and you leave yourself open to a version control
nightmare. What happens when you change your design master and distribute a
new MDE file? If the user *could* change the MDE then their changes would
be wiped out by the new file.

If your users want additional functionality then why not design it into your
master file?

Keith.
www.keithwilby.co.uk

Oct 31 '08 #4

P: n/a

"Keith Wilby" <he**@there.comschreef in bericht
news:49**********@glkas0286.greenlnk.net...
"susan" <vd*@hotmail.comwrote in message
news:66***************************@cache1.tilbu1.n b.home.nl...
>>
"Keith Wilby" <he**@there.comschreef in bericht
news:49**********@glkas0286.greenlnk.net...
>>"susan" <vd*@hotmail.comwrote in message
news:bb***************************@cache5.tilbu1 .nb.home.nl...
Hi,

Is it (in Access2003) possible yo link from a form in db1 to a form in
db2?
You can link tables, is that what you mean? What is it you're trying to
achieve?

Keith.
www.keithwilby.co.uk

db1 is a MDE. I distributed this to several users. There are users who
want to have extra options. I want to give them this possibility to let
them build themselves these extensions. Yherefor I want to create a
commandbutton "Extra" in db1 which links to a Form "MyExtras"in db2. From
this form the user can build his own extra functionality.

You can't make design changes to forms in an MDE. The scenario you
describe is an unorthadox one and you leave yourself open to a version
control nightmare. What happens when you change your design master and
distribute a new MDE file? If the user *could* change the MDE then their
changes would be wiped out by the new file.

If your users want additional functionality then why not design it into
your master file?

Keith.
www.keithwilby.co.uk
The users can't change the MDE (db1) but can change / build his forms in db2
(MDB). So I always keep my basic MDE. The personal additions are build in
dv2 and can be very different for each user.
When I modify and distribute a new MDE all the extras in the MDB can still
be used because of the link between db1 (MDE) and db2 (MDB).
Oct 31 '08 #5

P: n/a
"susan" <vd*@hotmail.comwrote in message
news:a0**************************@cache6.tilbu1.nb .home.nl...
>

The users can't change the MDE (db1) but can change / build his forms in
db2 (MDB). So I always keep my basic MDE. The personal additions are
build in dv2 and can be very different for each user.
When I modify and distribute a new MDE all the extras in the MDB can still
be used because of the link between db1 (MDE) and db2 (MDB).

Try this:

Dim objAccess As Access.Application
Set objAccess = New Access.Application
objAccess.OpenCurrentDatabase "\\MyPath\db2.mdb"
objAccess.Visible = True
objAccess.DoCmd.OpenForm "frmMyExtras", acViewNormal

Keith.

Oct 31 '08 #6

P: n/a

"Keith Wilby" <he**@there.comschreef in bericht
news:49**********@glkas0286.greenlnk.net...
"susan" <vd*@hotmail.comwrote in message
news:a0**************************@cache6.tilbu1.nb .home.nl...
>>

The users can't change the MDE (db1) but can change / build his forms in
db2 (MDB). So I always keep my basic MDE. The personal additions are
build in dv2 and can be very different for each user.
When I modify and distribute a new MDE all the extras in the MDB can
still be used because of the link between db1 (MDE) and db2 (MDB).


Try this:

Dim objAccess As Access.Application
Set objAccess = New Access.Application
objAccess.OpenCurrentDatabase "\\MyPath\db2.mdb"
objAccess.Visible = True
objAccess.DoCmd.OpenForm "frmMyExtras", acViewNormal

Keith.
Thanks Keith!

This works fine.
Is it also possible to open the form in the current application in stead of
a new application?

Oct 31 '08 #7

P: n/a
"susan" <vd*@hotmail.comwrote in
news:49***************************@cache6.tilbu1.n b.home.nl:
Is it also possible to open the form in the current application in
stead of a new application?
In [Northwinds 2007] I
1. Ensure that the Form “Customer Details” has a module, or has its
HasModule Property set to True.
2. I write this function:

Public Function GetCustomerDetails() As Form
Set GetCustomerDetails = [Form_Customer Details]
End Function

I close [Northwinds 2007]

In another database I set a reference to [Northwinds 2007]. (This may fail
if the already existing references of the two dbs are inconsistent so these
may have to be reconciled, example, making sure they are both referencing
the same version of ADODB.)

In the “another” database I write this function:

Public Sub ShowCustomerDetails()
Dim CustomerDetails As Form
Set CustomerDetails = [Northwind 2007].GetCustomerDetails
CustomerDetails.Visible = True
End Sub

ShowCustomerDetails now opens the Northwoods 2007 form, “Customer Details”.

Many will prefer putting a DoCmd.OpenForm etc. Procedure in Northwinds.

--
lyle fairfield
Oct 31 '08 #8

P: n/a
lyle fairfield wrote:
>"susan" <vd*@hotmail.comwrote
>Is it also possible to open the form in the current application in
stead of a new application?

In [Northwinds 2007] I
1. Ensure that the Form “Customer Details” has a module, or has its
HasModule Property set to True.
2. I write this function:

Public Function GetCustomerDetails() As Form
Set GetCustomerDetails = [Form_Customer Details]
End Function

I close [Northwinds 2007]

In another database I set a reference to [Northwinds 2007]. (This may fail
if the already existing references of the two dbs are inconsistent so these
may have to be reconciled, example, making sure they are both referencing
the same version of ADODB.)

In the “another” database I write this function:

Public Sub ShowCustomerDetails()
Dim CustomerDetails As Form
Set CustomerDetails = [Northwind 2007].GetCustomerDetails
CustomerDetails.Visible = True
End Sub

ShowCustomerDetails now opens the Northwoods 2007 form, “Customer Details”.

Many will prefer putting a DoCmd.OpenForm etc. Procedure in Northwinds.

Lyle, the trouble I have with a form/report kind of library
is figuring out how to set the form's record source to use a
table in the back end db. A single use library, such as
susan seems to need, can just link to the same tables as the
front end mde, but a multi purpose library has no idea
what/where back end tables/queries exist and IIRC always
uses its own db for its record source references to
tables/queries. Does anyone have a way to deal with this
issue?

--
Marsh
Nov 1 '08 #9

P: n/a
On Nov 1, 3:07*pm, Marshall Barton <marshbar...@wowway.comwrote:
lyle fairfield wrote:
"susan" <v...@hotmail.comwrote
Is it also possible to open the form in the current application in
stead of a new application?
In [Northwinds 2007] I
1. Ensure that the Form “Customer Details” has a module, or has its
HasModule Property set to True.
2. I write this function:
Public Function GetCustomerDetails() As Form
* *Set GetCustomerDetails = [Form_Customer Details]
End Function
I close [Northwinds 2007]
In another database I set a reference to [Northwinds 2007]. (This may fail
if the already existing references of the two dbs are inconsistent so these
may have to be reconciled, example, making sure they are both referencing
the same version of ADODB.)
In the “another” database I write this function:
Public Sub ShowCustomerDetails()
* *Dim CustomerDetails As Form
* *Set CustomerDetails = [Northwind 2007].GetCustomerDetails
* *CustomerDetails.Visible = True
End Sub
ShowCustomerDetails now opens the Northwoods 2007 form, “Customer Details”.
Many will prefer putting a DoCmd.OpenForm etc. Procedure in Northwinds.

Lyle, the trouble I have with a form/report kind of library
is figuring out how to set the form's record source to use a
table in the back end db. *A single use library, such as
susan seems to need, can just link to the same tables as the
front end mde, but a multi purpose library has no idea
what/where back end tables/queries exist and IIRC always
uses its own db for its record source references to
tables/queries. *Does anyone have a way to deal with this
issue?

--
Marsh
Years ago, with Access 97, we could fully expose forms. When we
referenced a db with exposed forms all their properties and methods
were available. But I have had no sucess in duplicating this complete
exposure with later Access versions.
Even when the external form can be opened, and its recordsource set,
it is, often (always?), not editable.
So, I tend to apply particular solutions to particular problems.
Sometimes my solution is to link to an ADP form and to set the form's
recordset to an ADODB recordset. This is highly configurable and the
data are completely editable.
Nov 2 '08 #10

P: n/a
lyle fairfield wrote:
>On Nov 1, 3:07*pm, Marshall Barton wrote:
>Lyle, the trouble I have with a form/report kind of library
is figuring out how to set the form's record source to use a
table in the back end db. *A single use library, such as
susan seems to need, can just link to the same tables as the
front end mde, but a multi purpose library has no idea
what/where back end tables/queries exist and IIRC always
uses its own db for its record source references to
tables/queries. *Does anyone have a way to deal with this
issue?

Years ago, with Access 97, we could fully expose forms. When we
referenced a db with exposed forms all their properties and methods
were available. But I have had no sucess in duplicating this complete
exposure with later Access versions.
Even when the external form can be opened, and its recordsource set,
it is, often (always?), not editable.
So, I tend to apply particular solutions to particular problems.
Sometimes my solution is to link to an ADP form and to set the form's
recordset to an ADODB recordset. This is highly configurable and the
data are completely editable.

That's the kind of thing I was leaning towards. Thanks for
the followup response, it's good to know that I wasn't
missing something obvious.

--
Marsh
Nov 2 '08 #11

This discussion thread is closed

Replies have been disabled for this discussion.