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

Compiling to A2000 in A2003... problems

P: n/a
Hi

I am using A2003 on XP. The client has A2000. So I have ensured that I have
developed based on A2000 and compiled as such.

I have found that in a number of cases now, I have used (what I thought) was
fairly standard methods & properties, but as it turns out, not so. I
install on the client's machine and recompile and have found that a method
is just not recognised in A2000. eg: in A2003, docmd.OpenReport includes
the 'OpenArgs' parameter. In A2000, there is no such parameter available.

I am wondering is there a way that when using A2003 (apart from what I'm
already doing), to ensure that I don't use methods that seems to only be
available in A2002-3 and not in A2000?

TIA
Michelle
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On Wed, 28 Jan 2004 19:31:20 +1000, "-Michelle-" <mi********@yahoo.com> wrote:
Hi

I am using A2003 on XP. The client has A2000. So I have ensured that I have
developed based on A2000 and compiled as such.

I have found that in a number of cases now, I have used (what I thought) was
fairly standard methods & properties, but as it turns out, not so. I
install on the client's machine and recompile and have found that a method
is just not recognised in A2000. eg: in A2003, docmd.OpenReport includes
the 'OpenArgs' parameter. In A2000, there is no such parameter available.

I am wondering is there a way that when using A2003 (apart from what I'm
already doing), to ensure that I don't use methods that seems to only be
available in A2002-3 and not in A2000?

TIA
Michelle


Actually, I've been wondering the same thing, and besides developing in the
older version to make sure you don't try to use newer features, I don't really
know a way. I can tell you the few things I know, though.

1. The OpenArgs parameter for reports was added in Access 2002.
2. The Replace function was added in Access 2000.
3. The Recordset property of forms was added in Access 2000.

And finally, I find Access 2000 to have too many bugs to be worth using,
myself, so if you can try to convince clients to at least upgrade to 2002,
that will save you some hassle.
Nov 12 '05 #2

P: n/a
Thanks very much for your information. It's much appreciated.

Michelle

PS: Have tried convincing clients to upgrade, but it's not happening any
time soon.
"Steve Jorgensen" <no****@nospam.nospam> wrote in message
news:ov********************************@4ax.com...
On Wed, 28 Jan 2004 19:31:20 +1000, "-Michelle-" <mi********@yahoo.com> wrote:
Hi

I am using A2003 on XP. The client has A2000. So I have ensured that I havedeveloped based on A2000 and compiled as such.

I have found that in a number of cases now, I have used (what I thought) wasfairly standard methods & properties, but as it turns out, not so. I
install on the client's machine and recompile and have found that a methodis just not recognised in A2000. eg: in A2003, docmd.OpenReport includes
the 'OpenArgs' parameter. In A2000, there is no such parameter available.
I am wondering is there a way that when using A2003 (apart from what I'm
already doing), to ensure that I don't use methods that seems to only be
available in A2002-3 and not in A2000?

TIA
Michelle

Actually, I've been wondering the same thing, and besides developing in

the older version to make sure you don't try to use newer features, I don't really know a way. I can tell you the few things I know, though.

1. The OpenArgs parameter for reports was added in Access 2002.
2. The Replace function was added in Access 2000.
3. The Recordset property of forms was added in Access 2000.

And finally, I find Access 2000 to have too many bugs to be worth using,
myself, so if you can try to convince clients to at least upgrade to 2002,
that will save you some hassle.

Nov 12 '05 #3

P: n/a
On 28 Jan 2004 14:25:27 -0000, Mike Storr wrote:
Path: news20.bellglobal.com!nf4.bellglobal.com!nf1.bellg lobal.com!nf3.bellglobal.com!news.uunet.ca!cyclone .bc.net!news.alt.net!news.bananasplit.info!news.di zum.com!sewer-output!mail2news
Date: 28 Jan 2004 14:25:27 -0000
Message-ID: <4PWOUUKO38014.3926736111@anonymous>
From: An****************@See.Comment.Header (Mike Storr)
Subject: Re: Compiling to A2000 in A2003... problems
Newsgroups: comp.databases.ms-access
X-No-Archive: Yes
References: <bv***********@otis.netspace.net.au>
Comments: This message did not originate from the above address.
It was remailed by two or more anonymous mail services.
Send complaints of REAL abuse to remaileradmin at optonline dot net.
Mail-To-News-Contact: ab***@dizum.com
Organization: ma*******@dizum.com
Lines: 54
Xref: nf1.bellglobal.com comp.databases.ms-access:783579

-Michelle- wrote:
Hi

I am using A2003 on XP. The client has A2000. So I have ensured that I have
developed based on A2000 and compiled as such.

I have found that in a number of cases now, I have used (what I thought) was
fairly standard methods & properties, but as it turns out, not so. I
install on the client's machine and recompile and have found that a method
is just not recognised in A2000. eg: in A2003, docmd.OpenReport includes
the 'OpenArgs' parameter. In A2000, there is no such parameter available.

I am wondering is there a way that when using A2003 (apart from what I'm
already doing), to ensure that I don't use methods that seems to only be
available in A2002-3 and not in A2000?

TIA
Michelle


Go tools options and select Turn Off New Features Added after 2000. Simple.

You could also look this up in Help.


This is the second time I've seen my name used in a remailed message that
is not mine. Is it insecurity, or immaturity that requires this person to
hide behind others?

--
Mike Storr
veraccess.com
Nov 12 '05 #4

P: n/a
An****************@See.Comment.Header (Mike Storr) wrote:
Comments: This message did not originate from the above address.
It was remailed by two or more anonymous mail services.
Send complaints of REAL abuse to remaileradmin at optonline dot net


This posting is a forgery. Mike Storr did not post it.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.