A2K App Seems To Run Under 2002 and 2003?

[(Pete Cresswell)]

I just took an app developed under Access 2000 to the client's site.

First PC I put it on had Access 2002 installed and the app opened right up - no
problems, no prompts....just opened up and ran A-OK.

Then they decided that the actual users should have Access 2003 installed
because the rest of their MS Office installs were 2003 - so we installed Access
2003 on the users' machines.

Then tested the app on one of the user's machines expecting something like a "do
you want to convert this database?" prompt...but no such prompt. Again, it
just opened and ran.
Finally, I took that version home with me and opened it up on my own PC under
Access 2002. To my surprise, it opened up again - no prompts. Only thing I
had to do to make it compile was set the MS Excel reference back to 9.0 from the
higher version that it seemed to have automagically been set on the client's PC.
This all sounds pretty good to me....maybe too good.....

Is it normal - can I just keep ping-ponging the development of this app
back-and-forth between 2000 and 2003?
--
PeteCresswell

[Douglas J. Steele]

The default file format of both Access 2002 and 2003 is the Access 2000 file
format, which certainly helps.

As long as you don't use any features of the new versions that weren't
available in Access 2000, you should be fine.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

"(Pete Cresswell)" <x@y.z> wrote in message
news:2p********************************@4ax.com...

I just took an app developed under Access 2000 to the client's site.

First PC I put it on had Access 2002 installed and the app opened right
up - no
problems, no prompts....just opened up and ran A-OK.

Then they decided that the actual users should have Access 2003 installed
because the rest of their MS Office installs were 2003 - so we installed
Access
2003 on the users' machines.

Then tested the app on one of the user's machines expecting something like
a "do
you want to convert this database?" prompt...but no such prompt. Again,
it
just opened and ran.
Finally, I took that version home with me and opened it up on my own PC
under
Access 2002. To my surprise, it opened up again - no prompts. Only
thing I
had to do to make it compile was set the MS Excel reference back to 9.0
from the
higher version that it seemed to have automagically been set on the
client's PC.
This all sounds pretty good to me....maybe too good.....

Is it normal - can I just keep ping-ponging the development of this app
back-and-forth between 2000 and 2003?
--
PeteCresswell

[Wayne Morgan]

The default file format in Access 2002 (XP) and 2003 is the 2000 file
format. There is an option in the Options dialog to change the default, but
even if you do, Access 2002 and 2003 will open a 2000 file without
prompting. Changing the default only changes the version of the file when
you create a new file.

--
Wayne Morgan
MS Access MVP
"(Pete Cresswell)" <x@y.z> wrote in message
news:2p********************************@4ax.com...

I just took an app developed under Access 2000 to the client's site.

First PC I put it on had Access 2002 installed and the app opened right
up - no
problems, no prompts....just opened up and ran A-OK.

Then they decided that the actual users should have Access 2003 installed
because the rest of their MS Office installs were 2003 - so we installed
Access
2003 on the users' machines.

Then tested the app on one of the user's machines expecting something like
a "do
you want to convert this database?" prompt...but no such prompt. Again,
it
just opened and ran.
Finally, I took that version home with me and opened it up on my own PC
under
Access 2002. To my surprise, it opened up again - no prompts. Only
thing I
had to do to make it compile was set the MS Excel reference back to 9.0
from the
higher version that it seemed to have automagically been set on the
client's PC.
This all sounds pretty good to me....maybe too good.....

Is it normal - can I just keep ping-ponging the development of this app
back-and-forth between 2000 and 2003?
--
PeteCresswell

[(Pete Cresswell)]

Per (Pete Cresswell):

Is it normal - can I just keep ping-ponging the development of this app
back-and-forth between 2000 and 2003?

Oops! I think that '"H" <[e-mail]' answered my question already in the
'New Access Version?' thread.

Sounds like Tools|Options|Advanced|Default File Format was defaulted to Access
2000 at the client's site.
--
PeteCresswell

[Wayne Morgan]

You may find the following articles interesting.

http://support.microsoft.com/default...b;en-us;319400
http://support.microsoft.com/default...b;en-us;810415
http://support.microsoft.com/default...b;en-us;278376

--
Wayne Morgan
MS Access MVP

[(Pete Cresswell)]

Per Wayne Morgan:

Access 2002 and 2003 will open a 2000 file without
prompting

But I do get that annoying macro prompt - that I'm hearing can only be avoided
by setting SecurityLevel=Low.
--
PeteCresswell

[Wayne Morgan]

No, that's not the only way, but is probably the most practical way unless
you have the money to buy a security certificate for code signing. I've
looked at the pricing of these, it's too high for me to justify it for
myself. Also (I believe), once you do sign the code, any change to the code
will require resigning.

--
Wayne Morgan
MS Access MVP
"(Pete Cresswell)" <x@y.z> wrote in message
news:74********************************@4ax.com...

Per Wayne Morgan:

Access 2002 and 2003 will open a 2000 file without
prompting

But I do get that annoying macro prompt - that I'm hearing can only be
avoided
by setting SecurityLevel=Low.

[(Pete Cresswell)]

Per Wayne Morgan:

You may find the following articles interesting.

http://support.microsoft.com/default...b;en-us;319400
http://support.microsoft.com/default...b;en-us;810415
http://support.microsoft.com/default...b;en-us;278376

Thanks. After reading them, it looks to me like as long as I avoid 2002
format (i.e. stick with 2000 as I planned or go with 2003) there's no problem.
--
PeteCresswell