Convert Access 2003 app to 2007, what to expect?

  • Thread starter Thread starter sandal
  • Start date Start date
S

sandal

I have shied away from Access 2007 because frankly it looks to be pretty
screwed up for developer types, and clients of developer types. However
one client is migrating to Office 2007 so I have to deal with converting
the application. I am considering keeping it in 2003 as a runtime,
sagekey says the the new version of their software can accomodate.

But if I were to move the app to Access 2007, what should I expect?

The app uses an activex control for email communication and I'll ask the
vendor (codestone, they are excellent) about this.

Backend is simple mdb, front end mdbs are linked to it.

Ribbon bar...the worst thing ever added to Access. I will need to turn
it off and use an activex control or something that allows me to have
standard toolbars, and my custom toolbars. I think I've seen such a
thing, but can't find the reference.

BTW, what will happen if the client simply tries to run my Access 2003
app in Access 2007? Will it run minus the toolbars?

I've begun reading about these issues but have not run into answers re
the above yet.
 
Well I can only tell you my findings:

Opening db's from 2003 in 2007 no problems so far. There could be a security
warning telling you to trust the code.

I've only used regular activeX and that caused no problem so far.
The ribbon: when converting you'll find your menubars in the AddIn tab. You
won't get a special menubar replacing the ribbon. If you want to get rid of
the ribbon you would have to write your own custom ribbon where you can place
your menubar options in. Removing the ribbon al together is not an option it
will always be there.

I must say that it took me a while to get used to but I think the ribbon is
a great feature. But it took some getting used to.

So try a copy of your db, convert it to access (or run compatibility mode)
and see what to expect.
 
Back
Top