Transfer Control From One Database to Another Using RunTime
Stewart Berman
The application consists of two database. The first one is launch using RunTime. When the user
clicks on the close button I would like to transfer control to the second database.
I tried:
Application.OpenCurrentDatabase <Full path/name of second database>, True, <Password of
Second database>
However that throws a you already have the database open error. To make sure something in the first
database did not actually have the second one open I built a database that consisted of a single
form with the above in its load event and got the same error. The error occurs using the full
version of Access 2007 so it is not a RunTime issue. The second database is local on my development
machine and not in use by anything when the error is thrown.
Is there anyway to transfer control from one database to another without instantiating another
instance of Access?
Alex Dybenko
there is an addin for 2000, but don't know if it works with 2007
http://www.trigeminal.com/lang/1033/utility.asp?ItemID=8
--
Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com
"Stewart Berman" <sabe...@nospam.nospam> wrote in message
news:618le51msrqvm7eel...@4ax.com...
Stewart Berman
protected databases.
Can you explain why the OpenCurrentDataase method fails? Is there anyway to stack commands for the
Access Application that will be run after the current database is closed? That would allow:
CloseCurrentDatabase
OpenCurrrentDatabase
To be stacked.
![Tony Toews [MVP]'s profile photo](http://lh3.googleusercontent.com/a-/ALV-UjVFNFhAO8kxGtutFBSPYzx5Lbrrty7WRKPHNhjuWtTEHvsoQdk=s40-c)
Tony Toews [MVP]
>Aside from the fact that it requires the VB6 runtime be installed
FWIW the VB6 runtime is installed as part of the OS in WIndows 2000,
XP, Vista and 7.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
Alex Dybenko
I think this is due to licensing for runtime - they made it with limited
capabilities
--
Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com
"Stewart Berman" <sabe...@nospam.nospam> wrote in message
news:jv9me5d1gl2rsa4re...@4ax.com...
Jeff Boyce
You're asking "how"...
But "why?" What will having a second db opened allow you to do?
Regards
Jeff Boyce
Microsoft Access MVP
--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.
Any code or psuedocode included in this post is offered "as is", with no
guarantee as to suitability.
You can thank the FTC of the USA for making this disclaimer
possible/necessary.
"Stewart Berman" <sabe...@nospam.nospam> wrote in message
news:618le51msrqvm7eel...@4ax.com...
David W. Fenton
news:#95Kqd#WKHA...@TK2MSFTNGP06.phx.gbl:
> What will having a second db opened allow you to do?
Exactly,
It could be that opening multiple instances of a single form will do
the job, or launching objects in a "library" database will do the
trick.
I've been programming Access since 1996 and never needed to launch a
second database even once.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Stewart Berman
databases.
In addition, the VB6 runtime support is limited to applications running in the 32 bit WOW
environment. It won't work once Office is available in a 64 bit version.
Stewart Berman
is easy to do -- it is about transferring control from one Access database to another within the
same instance of Access.
Stewart Berman
2007 not just the RunTime version so it is not a matter of a RunTime limitation.
"Alex Dybenko" <ale...@PLEASE.cemi.NO.rssi.SPAM.ru> wrote:
>Hi,
Alex Dybenko
have you tried this method?
http://support.microsoft.com/kb/235422
--
Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com
"Stewart Berman" <sabe...@nospam.nospam> wrote in message
news:o8k4f5hopbnojevrh...@4ax.com...
Jeff Boyce
to do this, how do you expect us to offer relevant suggestions? You have
apparently already decided that the solution to your issue is to open a
second db and transfer control ... what issue? Are you open to the
possibility that there are other solutions?
Good luck!
Regards
Jeff Boyce
Microsoft Access MVP
--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.
Any code or psuedocode included in this post is offered "as is", with no
guarantee as to suitability.
You can thank the FTC of the USA for making this disclaimer
possible/necessary.
"Stewart Berman" <sabe...@nospam.nospam> wrote in message
news:15j4f5d34ao195j5f...@4ax.com...
Tony Toews [MVP]
>You should have included the rest of my statement: ... it does not support password protected
>databases.
Why? I wasn't commenting on that portion of your statement.
>In addition, the VB6 runtime support is limited to applications running in the 32 bit WOW
>environment. It won't work once Office is available in a 64 bit version.
I fail to see how the VB 6 runtime has nothing to do with 64 bit
Office. Which will be available in Office 2010.
Tony Toews [MVP]
>>In addition, the VB6 runtime support is limited to applications running in the 32 bit WOW
>>environment. It won't work once Office is available in a 64 bit version.
>
>I fail to see how the VB 6 runtime has nothing to do with 64 bit
>Office. Which will be available in Office 2010.
Whoops. I reworded the sentence and now it doesn't make sense.
I fail to see how the VB 6 runtime has anything to do with 64 bit
David W. Fenton
> You should have included the rest of my statement
You know what? You may not realize it, but you're coming across like
an asshole.
Why don't you take a deep breath for a moment and then try again
with an explanation of the problem you're trying to solve, instead
of starting with a solution and asking how to implement it?
Jim Franklin
So far you have given an inadequate explanation of the problem, and insulted
everyone who has tried to help you! Not a good recipe for getting people to
offer solutions...
Opening another database when closing one is easy. Running code
automatically in the 2nd database is easy. (I know, I have code which
periodically checks for a later version of the Access app, if it finds it it
closes the application, runs an Updater database to copy across the latest
version, then re-opens the later version. All works seamlessly and
automatically.)
Jim
"Stewart Berman" <sabe...@nospam.nospam> wrote in message
news:618le51msrqvm7eel...@4ax.com...
loucarey
I'm trying to do what you describe for updating a database. Could you please share your method for doing this?
Thanks,
Lou
Jim Franklin wrote:
Stewart, what is it exactly you are trying to do?
14-Nov-09
Stewart, what is it exactly you are trying to do?
So far you have given an inadequate explanation of the problem, and insulted
everyone who has tried to help you! Not a good recipe for getting people to
offer solutions...
Opening another database when closing one is easy. Running code
automatically in the 2nd database is easy. (I know, I have code which
periodically checks for a later version of the Access app, if it finds it it
closes the application, runs an Updater database to copy across the latest
version, then re-opens the later version. All works seamlessly and
automatically.)
Jim
Previous Posts In This Thread:
On Friday, October 30, 2009 4:21 AM
Stewart Berman wrote:
Transfer Control From One Database to Another Using RunTime
Access 2007 RunTime
The application consists of two database. The first one is launch using RunTime. When the user
clicks on the close button I would like to transfer control to the second database.
I tried:
Application.OpenCurrentDatabase <Full path/name of second database>, True, <Password of
Second database>
However that throws a you already have the database open error. To make sure something in the first
database did not actually have the second one open I built a database that consisted of a single
form with the above in its load event and got the same error. The error occurs using the full
version of Access 2007 so it is not a RunTime issue. The second database is local on my development
machine and not in use by anything when the error is thrown.
Is there anyway to transfer control from one database to another without instantiating another
instance of Access?
On Friday, October 30, 2009 4:36 AM
Alex Dybenko wrote:
Hi,there is an addin for 2000, but do not know if it works with 2007http://www.
Hi,
there is an addin for 2000, but do not know if it works with 2007
http://www.trigeminal.com/lang/1033/utility.asp?ItemID=8
--
Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com
On Friday, October 30, 2009 1:57 PM
Stewart Berman wrote:
Aside from the fact that it requires the VB6 runtime be installed it does not
Aside from the fact that it requires the VB6 runtime be installed it does not support password
protected databases.
Can you explain why the OpenCurrentDataase method fails? Is there anyway to stack commands for the
Access Application that will be run after the current database is closed? That would allow:
CloseCurrentDatabase
OpenCurrrentDatabase
To be stacked.
On Friday, October 30, 2009 4:33 PM
Tony Toews [MVP] wrote:
FWIW the VB6 runtime is installed as part of the OS in WIndows 2000,XP, Vista
FWIW the VB6 runtime is installed as part of the OS in WIndows 2000,
XP, Vista and 7.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
On Saturday, October 31, 2009 4:28 AM
Alex Dybenko wrote:
Hi,I think this is due to licensing for runtime - they made it with
Hi,
I think this is due to licensing for runtime - they made it with limited
capabilities
--
Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com
On Monday, November 02, 2009 1:07 PM
Jeff Boyce wrote:
StewartYou're asking "how"...But "why?
Stewart
You're asking "how"...
But "why?" What will having a second db opened allow you to do?
Regards
Jeff Boyce
Microsoft Access MVP
--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.
Any code or psuedocode included in this post is offered "as is", with no
guarantee as to suitability.
You can thank the FTC of the USA for making this disclaimer
possible/necessary.
On Tuesday, November 03, 2009 7:57 PM
David W. Fenton wrote:
Exactly,It could be that opening multiple instances of a single form will
Exactly,
It could be that opening multiple instances of a single form will do
the job, or launching objects in a "library" database will do the
trick.
I have been programming Access since 1996 and never needed to launch a
second database even once.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
On Wednesday, November 04, 2009 11:12 PM
Stewart Berman wrote:
You should have included the rest of my statement: ...
You should have included the rest of my statement: ... it does not support password protected
databases.
In addition, the VB6 runtime support is limited to applications running in the 32 bit WOW
environment. It will not work once Office is available in a 64 bit version.
On Wednesday, November 04, 2009 11:13 PM
Stewart Berman wrote:
Your question has no relevance to the current thread.
Your question has no relevance to the current thread. It is not about opening a second db -- which
is easy to do -- it is about transferring control from one Access database to another within the
same instance of Access.
On Wednesday, November 04, 2009 11:15 PM
Stewart Berman wrote:
If you read the beginning of the thread you will see that I tried it in the
If you read the beginning of the thread you will see that I tried it in the full version of Access
2007 not just the RunTime version so it is not a matter of a RunTime limitation.
On Wednesday, November 04, 2009 11:53 PM
Alex Dybenko wrote:
Hi,have you tried this method?
Hi,
have you tried this method?
http://support.microsoft.com/kb/235422
--
Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com
On Thursday, November 05, 2009 10:35 AM
Jeff Boyce wrote:
If you do not provide sufficient background for us to understand why you
If you do not provide sufficient background for us to understand why you wish
to do this, how do you expect us to offer relevant suggestions? You have
apparently already decided that the solution to your issue is to open a
second db and transfer control ... what issue? Are you open to the
possibility that there are other solutions?
Good luck!
Regards
Jeff Boyce
Microsoft Access MVP
--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.
Any code or psuedocode included in this post is offered "as is", with no
guarantee as to suitability.
You can thank the FTC of the USA for making this disclaimer
possible/necessary.
On Saturday, November 07, 2009 4:57 PM
Tony Toews [MVP] wrote:
Why?
Why? I was not commenting on that portion of your statement.
I fail to see how the VB 6 runtime has nothing to do with 64 bit
Office. Which will be available in Office 2010.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
On Saturday, November 07, 2009 5:06 PM
Tony Toews [MVP] wrote:
Whoops. I reworded the sentence and now it does not make sense.
Whoops. I reworded the sentence and now it does not make sense.
I fail to see how the VB 6 runtime has anything to do with 64 bit
Office. Which will be available in Office 2010.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
On Saturday, November 14, 2009 8:06 PM
Jim Franklin wrote:
Stewart, what is it exactly you are trying to do?
Stewart, what is it exactly you are trying to do?
So far you have given an inadequate explanation of the problem, and insulted
everyone who has tried to help you! Not a good recipe for getting people to
offer solutions...
Opening another database when closing one is easy. Running code
automatically in the 2nd database is easy. (I know, I have code which
periodically checks for a later version of the Access app, if it finds it it
closes the application, runs an Updater database to copy across the latest
version, then re-opens the later version. All works seamlessly and
automatically.)
Jim
Submitted via EggHeadCafe - Software Developer Portal of Choice
C# : row-clickable GridView and get and set gridview rows using JavaScript
http://www.eggheadcafe.com/tutorials/aspnet/7ab7fa12-a697-4b26-9465-c45307bae45b/c--rowclickable-gridvi.aspx
Tony Toews [MVP]
>I'm trying to do what you describe for updating a database. Could you please share your method for doing this?
I specifically created the Auto FE Updater utility so that I could
make changes to the FE MDE as often as I wanted and be quite confident
that the next time someone went to run the app that it would pull in
the latest version. For more info on the errors or the free Auto FE
Updater utility see http://www.autofeupdater.com to keep the FE on
each PC up to date.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files