Re: Access 2003 and Access 2007 on same machine
- From: Dennis <druppert@xxxxxxxxxxxxxx>
- Date: Sun, 12 Aug 2007 09:11:20 -0700
On Aug 12, 8:39 am, "Rick Brandt" <rickbran...@xxxxxxxxxxx> wrote:
Dennis wrote:
Rick,
I have read your posts over the years, and I respect your knowledge. I
figure if you are unaware of a work-around for this problem, then
there probably isn't one. :-(
The more I think about it, the more absurd this seems. At least I know
now that I am not alone. I thought I was missing some obvious
solution.
Install your app in a version that will work for the user. I think that is
obvious. Actually, that sounds a bit pretentious on my part so let me clairify.
As I see it there are two kinds of Access developers. The majority (I believe)
are those that work with a client to deliver an Access solution that suits their
needs. In that situation you would evaluate what the users have already
installed and would simply NOT deliver an Access solution that will give them
problems such as those being described. If that means delivering an older
version then that is exactly what should be done.
The second type is the developer who builds a generic app with his preferred
specific version and then tries to sell it to people. In that case you simply
have to indicate in the specifications where that application will work, where
it will not work, and where it will work, but introduce such problems. This is
no different than indicatiing a minimum resolution, processor, or RAM
specification.
If the first type of developer wants to state at the beginning of the discussion
"I only use Access 2007 and it will introduce problems on your system unless you
upgrade all Office apps to 2007", then I would say that the developer is not
really interested in making a living with Access.
I just had a thought. I wonder if it would be possible to build a
small VB app that would recognize the title bar of the install dialog
box, then kill the process. Maybe that would hose up the Access
loading process, I don't know. I know enough VB6 to give it a go, but
perhaps I'm way off base with the idea.
Sorry, but I don't understand what you are proposing here.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Rick,
I was just "thinking out loud".
Something along these lines;
Make a stand alone application, let's just say; "Launch Access.exe".
Use this app to launch Access, with a choice of which Access version
you want to use. The app uses Windows APIs, detects that the install
dialog has opened, and then kills that process. Of course even if this
was possible, it still wouldn't help with double-clicking to open the
app.
As I said, just a theoretical idea, and probably not possible because
the install dialog is not really an application in its self.
I have used the APIs to detect if an Access application was already
open to prevent launching another copy, and also to see if Outlook was
open.
Hey, never hurts to theorize, does it?
Dennis
.
- Follow-Ups:
- Re: Access 2003 and Access 2007 on same machine
- From: Sascha Trowitzsch
- Re: Access 2003 and Access 2007 on same machine
- References:
- Access 2003 and Access 2007 on same machine
- From: Dennis
- Re: Access 2003 and Access 2007 on same machine
- From: Salad
- Re: Access 2003 and Access 2007 on same machine
- From: Wayne
- Re: Access 2003 and Access 2007 on same machine
- From: Salad
- Re: Access 2003 and Access 2007 on same machine
- From: Rick Brandt
- Re: Access 2003 and Access 2007 on same machine
- From: Dennis
- Re: Access 2003 and Access 2007 on same machine
- From: Rick Brandt
- Access 2003 and Access 2007 on same machine
- Prev by Date: Re: Create Weekly and Monthly Flag in database/table
- Next by Date: Re: Sub routine syntax errors
- Previous by thread: Re: Access 2003 and Access 2007 on same machine
- Next by thread: Re: Access 2003 and Access 2007 on same machine
- Index(es):
Relevant Pages
|
