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

Upgrading from 2002

P: n/a
Popping out of lurkdom for a moment. I've got a 2003 upgrade package
here on my desk. Should I skip it and head straight to 2007?
Thoughts?

All the databases I'm supporting or writing are in 2000 format. I've
kept an install of 97, just in case, but I think it may be safe to
ditch it now.

Tia

Oct 15 '07 #1
Share this Question
Share on Google+
13 Replies


P: n/a
By all means, grab a copy of 2007 and start learning it. It's a major new
release, and you do need to become familiar with it. But don't actually
trust anything significant to it until Serivce Pack 1 is released, as it's
not usable yet.

Details:
http://allenbrowne.com/Access2007.html

You may want to keep your copy of A2000 on your computer as well. Although
A2007 can handle A2000 mdb files natively, it looks quite different, and
there are some things that are easier to do with the older version (e.g. if
you must modify a custom menu/toolbar.)

Welcome from the shadows of lurkdom. :0)

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<pa*******@aol.comwrote in message
news:11**********************@k35g2000prh.googlegr oups.com...
Popping out of lurkdom for a moment. I've got a 2003 upgrade package
here on my desk. Should I skip it and head straight to 2007?
Thoughts?

All the databases I'm supporting or writing are in 2000 format. I've
kept an install of 97, just in case, but I think it may be safe to
ditch it now.

Tia
Oct 15 '07 #2

P: n/a
It might pay to have a look at this first: http://allenbrowne.com/Access2007.html.
Personally I'm finding there's still a few too many issues and I'm
sticking with A2003 at least until A2007 SP1 has been released.
Oct 15 '07 #3

P: n/a
Oops. Looks like Allen and I posted at the same time.
Oct 15 '07 #4

P: n/a
I havent used access 2007 much...so my opinion is fairly worthless..

Ribbons are annoying as hell! :)

John

<pa*******@aol.comwrote in message
news:11**********************@k35g2000prh.googlegr oups.com...
Popping out of lurkdom for a moment. I've got a 2003 upgrade package
here on my desk. Should I skip it and head straight to 2007?
Thoughts?

All the databases I'm supporting or writing are in 2000 format. I've
kept an install of 97, just in case, but I think it may be safe to
ditch it now.

Tia

Oct 15 '07 #5

P: n/a
On Oct 14, 9:43 pm, "Allen Browne" <AllenBro...@SeeSig.Invalidwrote:
By all means, grab a copy of 2007 and start learning it. It's a major new
release, and you do need to become familiar with it. But don't actually
trust anything significant to it until Serivce Pack 1 is released, as it's
not usable yet.
So, can we just return it for a full refund?

Oct 15 '07 #6

P: n/a
I won't say your opinion is worthless, John. In fact, it's probably a fairly
common reaction from someone familiar with menus and toolbars, but not
familiar with the new interface yet.

If you do want some help to find your way, MS has published a few tools.
Here's a farily new interactive one (Flash based) that lets you start with
what you know in A2003, and learn where it's found in the ribbon:
http://office.microsoft.com/en-us/ac...388991033.aspx

If you prefer an Excel workbook to look up:
http://office.microsoft.com/search/r...HA101666061033

We will have to adapt at some point, so hope that helps ease the pain.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"John" <no****@nospam.comwrote in message
news:fe*********@news5.newsguy.com...
>I havent used access 2007 much...so my opinion is fairly worthless..

Ribbons are annoying as hell! :)

John
Oct 15 '07 #7

P: n/a
"Allen Browne" <Al*********@SeeSig.Invalidwrote in
news:47***********************@per-qv1-newsreader-01.iinet.net.au:
We will have to adapt at some point, so hope that helps ease the
pain.
No, we don't have to adapt. I never learned ADO, for instance,
despite all the assertions by everybody in the know that everyone
would "have to adapt at some point."

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Oct 15 '07 #8

P: n/a
So, can we just return it for a full refund?

Lyle, I just love your dry wit. I'm sure some of the comments that
you post on this newsgroup bring amusement to many, including myself.
This one is certainly food for thought though. Why do we routinely
accept software that doesn't work properly and sometimes after several
"updates" or "service packs" still doesn't work properly.

Some of the Access bugs that continue in version after version as
outlined on Allen's website are just an example.

In many, many other retail areas this is totally unacceptable. If I
purchase a new TV that doesn't work properly, I take it back and get a
replacement. If I purchase a new car that has problems, the
manufacturer is obliged to fix the problems free of charge. Why
should software be any different? Somehow I can't see anything
changing in the near term. Our acceptance of the current situation as
consumers will guarantee this.
Oct 16 '07 #9

P: n/a

"Wayne" <cq*******@volcanomail.comschreef in bericht news:11**********************@t8g2000prg.googlegro ups.com...

I totally agree Wayne.
It is a shame that M$ treats their customers like that.

But some here will say: "Don't bite the hand that feeds you..." or something like that.
Some of the Access bugs that continue in version after version as
outlined on Allen's website are just an example.
The Developers-Kit is another example.
==I lost many, many hours with that crap !!
Sometimes a runtime distributed with it totally 'messed up' other MS-Office installs !!
We just could not *reliably* install a runtime without software like SageKey and/or Wise.
Sagekey was able to figure it out. M$ was not capable of doing just that (or just didn't want to ???)

Arno R
Oct 16 '07 #10

P: n/a
Allen wrote:
don't actually trust anything
significant to it until Serivce Pack 1 is released,
LOL. Taking Allen's advice has worked before, so I'll dabble in
2007.

But to get the bills paid, looks like multiple versions (again) is the
way to go for now. THANKS for the links & pain savings. I'm pain
intolerant.

At least 2003 has DAO as default. That'll be nice. As soon as I
figure out how to turn off those annoying warnings about labels
unconnected to their fields (agh! gods help us -- free radical labels
on the loose), I bet I'll be able to stop whining and look ahead to a
bold new future of . . . ribbons?

Tia

Oct 16 '07 #11

P: n/a
To turn off the warning about the unattached labels in design view, go to:
Office Button | Access Options | Object Designers
and scroll down to Error Checking.

The only one I uncheck is:
Check for unassociated label and control
leaving "Check for New ..." checked, so it only flags the new ones, not the
ones that were saved previously.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<pa*******@aol.comwrote in message
news:11**********************@t8g2000prg.googlegro ups.com...
Allen wrote:
>don't actually trust anything
significant to it until Serivce Pack 1 is released,

LOL. Taking Allen's advice has worked before, so I'll dabble in
2007.

But to get the bills paid, looks like multiple versions (again) is the
way to go for now. THANKS for the links & pain savings. I'm pain
intolerant.

At least 2003 has DAO as default. That'll be nice. As soon as I
figure out how to turn off those annoying warnings about labels
unconnected to their fields (agh! gods help us -- free radical labels
on the loose), I bet I'll be able to stop whining and look ahead to a
bold new future of . . . ribbons?

Tia
Oct 16 '07 #12

P: n/a
But to get the bills paid, looks like multiple versions (again) is the
way to go for now. THANKS for the links & pain savings. I'm pain
intolerant.
If you're pain intolerant, which I think most of us are, you're not
going to like running A2007 and earlier versions on the same machine.
This is a classic example of something that MS was obviously aware of
but chose to do nothing about.

I think I've seen somewhere on this forum that they are going to
address the problem in SP1, but I'm not holding my breath.

Oct 17 '07 #13

P: n/a
Ribbons are annoying as hell! :)

I'm not sure I understand the hatred of the Ribbon UI. I find it to be
very powerful, and pretty darn easy to use. I like it better than
custom menus from a functionality standpoint, and aesthetically, the
Ribbon blows menus away. I love the consistency across Office.

Kind of reminds me of all the negativity over Vista. With some *large*
exceptions, overall, Vista is awesome.

Oct 20 '07 #14

This discussion thread is closed

Replies have been disabled for this discussion.