Hi,
Is it (in Access2003) possible yo link from a form in db1 to a form in db2?
Thanks,
Susan
Is it (in Access2003) possible yo link from a form in db1 to a form in db2?
Thanks,
Susan
-
-
Re: link to form in other db
"susan" <vdb@hotmail.co mwrote in message
news:bb7cd$490a b48f$524b0a9c$2 7015@cache5.til bu1.nb.home.nl. ..You can link tables, is that what you mean? What is it you're trying toHi,
>
Is it (in Access2003) possible yo link from a form in db1 to a form in
db2?
>
achieve?
Keith.
-
Re: link to form in other db
"Keith Wilby" <here@there.com schreef in bericht
news:490ac0d4$1 _1@glkas0286.gr eenlnk.net...db1 is a MDE. I distributed this to several users. There are users who want"susan" <vdb@hotmail.co mwrote in message
news:bb7cd$490a b48f$524b0a9c$2 7015@cache5.til bu1.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
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"i n db2. From this form the
user can build his own extra functionality.
Comment
-
Re: link to form in other db
"susan" <vdb@hotmail.co mwrote in message
news:66419$490a c794$524b0a9c$2 7392@cache1.til bu1.nb.home.nl. ..You can't make design changes to forms in an MDE. The scenario you describe>
"Keith Wilby" <here@there.com schreef in bericht
news:490ac0d4$1 _1@glkas0286.gr eenlnk.net...>>"susan" <vdb@hotmail.co mwrote in message
>news:bb7cd$490 ab48f$524b0a9c$ 27015@cache5.ti lbu1.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"i n db2. From
this form the user can build his own extra functionality.
>
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.
Comment
-
Re: link to form in other db
"Keith Wilby" <here@there.com schreef in bericht
news:490ac7c5$1 _1@glkas0286.gr eenlnk.net...The users can't change the MDE (db1) but can change / build his forms in db2"susan" <vdb@hotmail.co mwrote in message
news:66419$490a c794$524b0a9c$2 7392@cache1.til bu1.nb.home.nl. ..>>>
>"Keith Wilby" <here@there.com schreef in bericht
>news:490ac0d4$ 1_1@glkas0286.g reenlnk.net...>>>>"susan" <vdb@hotmail.co mwrote in message
>>news:bb7cd$49 0ab48f$524b0a9c $27015@cache5.t ilbu1.nb.home.n l...
>>>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
>commandbutto n "Extra" in db1 which links to a Form "MyExtras"i n 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
(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).
Comment
-
Re: link to form in other db
"susan" <vdb@hotmail.co mwrote in message
news:a0486$490a d1b8$524b0a9c$9 354@cache6.tilb u1.nb.home.nl.. .Try this:>
>
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).
>
>
Dim objAccess As Access.Applicat ion
Set objAccess = New Access.Applicat ion
objAccess.OpenC urrentDatabase "\\MyPath\db2.m db"
objAccess.Visib le = True
objAccess.DoCmd .OpenForm "frmMyExtra s", acViewNormal
Keith.
Comment
-
Re: link to form in other db
"Keith Wilby" <here@there.com schreef in bericht
news:490ad199$1 _1@glkas0286.gr eenlnk.net...Thanks Keith!"susan" <vdb@hotmail.co mwrote in message
news:a0486$490a d1b8$524b0a9c$9 354@cache6.tilb u1.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.Applicat ion
Set objAccess = New Access.Applicat ion
objAccess.OpenC urrentDatabase "\\MyPath\db2.m db"
objAccess.Visib le = True
objAccess.DoCmd .OpenForm "frmMyExtra s", acViewNormal
>
Keith.
This works fine.
Is it also possible to open the form in the current application in stead of
a new application?
Comment
-
Re: link to form in other db
"susan" <vdb@hotmail.co mwrote in
news:493f1$490a f7b7$524b0a9c$2 6243@cache6.til bu1.nb.home.nl:
In [Northwinds 2007] IIs it also possible to open the form in the current application in
stead of a new application?
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 GetCustomerDeta ils() As Form
Set GetCustomerDeta ils = [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 ShowCustomerDet ails()
Dim CustomerDetails As Form
Set CustomerDetails = [Northwind 2007].GetCustomerDet ails
CustomerDetails .Visible = True
End Sub
ShowCustomerDet ails now opens the Northwoods 2007 form, “Customer Details”.
Many will prefer putting a DoCmd.OpenForm etc. Procedure in Northwinds.
--
lyle fairfield
Comment
-
Re: link to form in other db
lyle fairfield wrote:
>"susan" <vdb@hotmail.co mwrote
>>>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 GetCustomerDeta ils() As Form
Set GetCustomerDeta ils = [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 ShowCustomerDet ails()
Dim CustomerDetails As Form
Set CustomerDetails = [Northwind 2007].GetCustomerDet ails
CustomerDetails .Visible = True
>End Sub
>
>ShowCustomerDe tails 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
Comment
-
Re: link to form in other db
On Nov 1, 3:07 pm, Marshall Barton <marshbar...@wo wway.comwrote:Years ago, with Access 97, we could fully expose forms. When welyle fairfield wrote:>"susan" <v...@hotmail.c omwrote>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 GetCustomerDeta ils() As Form
Set GetCustomerDeta ils = [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 ShowCustomerDet ails()
Dim CustomerDetails As Form
Set CustomerDetails = [Northwind 2007].GetCustomerDet ails
CustomerDetails .Visible = True
End Sub>ShowCustomerDet ails 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
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.
Comment
-
Re: link to form in other db
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
Comment
Comment