Backwards compatibility

[mjbaz]

Hi Everyone:

I am experiencing a problem which may have something to do with
different Access versions.

Approximately 4 years ago, I wrote a small program for a law firm.
They recently contacted me requesting some updates. When I attempted
to install these updates I experienced some problems. Unfortunately, I
cannot recall the exact error but it occurred when attempting to open
the main form of the program.

I believe I may have isolated the problem down to one line of code:

RunCommand acCmdRecordsGoToNew

This command is used to return to the current record after a requery.

I am currently using Access 2002 (10.6501.6735)SP3 to develop and/or
edit existing programs. This law firm, however, is still using Access
2000 (9.0.2720). Could this be the problem? And does anyone know of
alternative code to achieve the same result.

Thanking all in advance for responding. This newsgroup is great - I
have learn so much from it.

Regards,
Michael Baz

[Jana]

Michael:

Not sure if this will help, but you can use the following to replace
your code:

DoCmd.GoToRecord , , acNewRec

I believe that the DoCmd action is considered 'newer' than the
RunCommand action, but I wouldn't stake my life on it.

HTH,
Jana

[Albert D. Kallal]

>

I am experiencing a problem which may have something to do with
different Access versions.
Yes, the above makes sense.

First, there are some new features. For example, the openreport got extra
features in a2002
(the model option for example)

I was under the impression that if you used a2000 file format, then the
extra features were not available (but, I am wrong!!).

You can likely develop on a2002, but right before you deploy, you need to do
a de-compile on your machine, and then re-compile the code on the target
computer. (or, have a machine on your location that has 2000 on it). You
likely should also be deploying a mde also.

So, I would compile your code on a a2000 box, as that is what the client is
running. It is indeed silly to risk your reputation, or the clients data
simply because you are mixing, and matching versions of ms-access.

I believe I may have isolated the problem down to one line of code:

RunCommand acCmdRecordsGoToNew

Hum, I never used the above form, and always used the docmand.GotoReocrd...

So, I like Jana's suggestion to use GoToReocrd.

You really don't want to start writing different code for each version...

You could also dry doing a de-compile right before you send it to the
client, but for safety, if you want to have any level of professionalism
here, you likely should de-compile (MUST DO!!), and THEN compile it in a2000
before you send it to the client. And, I have to assume you are using a
split database (or, do hey shut down the firm, and not use your software
while you work on it?).

You can read about splitting here, as this process helps the development
process, and also allows multi-user

http://www.members.shaw.ca/AlbertKal...plit/index.htm

You can read about de-compile here:
http://www.mvps.org/access/bugs/bugs0008.htm

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal