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

Message to users running lower version Access

P: n/a
Hi ,

I'm wondering it there is a way to notify users of the need to use a
different version of Access (2003). I have an Access 2003 mde file that
can't be opened by Access 2000-2002 users. I would like to pop up a message
(instead of the Access error message that it does not recognize the format),
telling the user that they need to be running Access 2003.

A background note - I am developing in 2002/2003 format on a machine running
2003, so I produce the mde in 2003. As I recall, there was a need to move to
the 2002-2003 environment from 2000 because of the need to use OpenArgs when
using DoCmd.OpenReport (as 2000 did not have an OpenArgs parameter option).

Any help is appreciated,

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200702/1

Feb 9 '07 #1
Share this Question
Share on Google+
5 Replies


P: n/a
jamcompany via AccessMonster.com wrote:
Hi ,

I'm wondering it there is a way to notify users of the need to use a
different version of Access (2003). I have an Access 2003 mde file
that can't be opened by Access 2000-2002 users. I would like to pop
up a message (instead of the Access error message that it does not
recognize the format), telling the user that they need to be running
Access 2003.

A background note - I am developing in 2002/2003 format on a machine
running 2003, so I produce the mde in 2003. As I recall, there was a
need to move to the 2002-2003 environment from 2000 because of the
need to use OpenArgs when using DoCmd.OpenReport (as 2000 did not
have an OpenArgs parameter option).

Any help is appreciated,
In order to run your code that displays your message the file would need to be
successfully opened which is impossible when they have the wrong version.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Feb 10 '07 #2

P: n/a
Ugh - that's what I suspected. Did I just paint myself into a corner by
implementing a new OpenReport method (one with the OpenArgs parameter)? I
really didn't see another choice in order to get the functionality I needed
on the report side of the application.

Any suggestions?

Rick Brandt wrote:
>Hi ,
[quoted text clipped - 12 lines]
>>
Any help is appreciated,

In order to run your code that displays your message the file would need to be
successfully opened which is impossible when they have the wrong version.
--
Phil

Message posted via http://www.accessmonster.com

Feb 10 '07 #3

P: n/a
jamcompany via AccessMonster.com wrote:
Ugh - that's what I suspected. Did I just paint myself into a corner
by implementing a new OpenReport method (one with the OpenArgs
parameter)? I really didn't see another choice in order to get the
functionality I needed on the report side of the application.

Any suggestions?
I have no idea what you are talking about with your report. A user with the
wrong version will get an error. When they ask about it tell them they have the
wrong version. Happens all the time with software.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Feb 10 '07 #4

P: n/a

"jamcompany via AccessMonster.com" <u19089@uweschreef in bericht news:6d9278c47eaa0@uwe...
Ugh - that's what I suspected. Did I just paint myself into a corner by
implementing a new OpenReport method (one with the OpenArgs parameter)? I
really didn't see another choice in order to get the functionality I needed
on the report side of the application.

Any suggestions?
Use Access2000 to develop, and you can deploy your mdb/mde to anyone who has A2000, A2002 or A2003.
Tell us what you are trying to achieve with the openargs
I guess you must be able to find a workaround for the openargs param of your report.

Arno R
Feb 10 '07 #5

P: n/a
Bri
jamcompany via AccessMonster.com wrote:
Ugh - that's what I suspected. Did I just paint myself into a corner by
implementing a new OpenReport method (one with the OpenArgs parameter)? I
really didn't see another choice in order to get the functionality I needed
on the report side of the application.

Any suggestions?
If the openargs value is coming from a calling form, then you could just
refer back to that form to get the value.

eg.
Where Me!MyOption is a control on the form that holds the value the
OpenArg (it can be a hidden control that is used just to hold this value).

If the code in the calling form is something like:
DoCmd.OpenReport "MyReport",,,,Me!MyOption

Then instead do something like this in the On_Open event code:
Select Case Forms!MyForm!MyOption
Case 1
'Do some stuff
Case 2
'Do other stuff
Case 3
'And so on
End Select

Hopefully that will give some ideas on how to get around the OpenArgs.
I've done this sort of thing myself as I primarily code in AC97 and then
convert as needed.

--
Bri
Feb 10 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.