Access 2007
(1)
Access 2003
(1)
Office 2003
(1)
Office 2007
(1)
VBA
(1)
Database
(1)
TWickerath
(1)
Bontrager
(1)

Convert from Acess 2003 to 2007

Asked By Paul
02-Feb-10 02:13 PM
Our office is converting from Office 2003 to Office 2007 the middle of Feb
2010. I am currently the administrator (additional duty) on an Access 2003
front end - back end system with an updater_launcher. Our database uses the
full range of objects: tables, queries, forms, reports, macros, and modules.
Microsoft makes it sound easy to convert a database to Access 2007 format
(see their link at
http://office.microsoft.com/en-us/access/HA100484061033.aspx). Is it really
as simple as they make it appear, or should I expect problems by using their
approach? Any advise would be greatly appreciated. Thanks.

Don't do it.

Jerry Whittle replied to Paul
02-Feb-10 02:36 PM
Don't do it. You can still use the 2003 mdb/mde database format with Access
2007.

Do you use user-level security? If you convert to the new 2007 accdb format,
you will not. It does not support it. So if you need user-level security, you
must stay with the Access 2003 file format.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

Hi Paul,Sometimes it is, and sometimes it is not.

Tom Wickerath replied to Paul
02-Feb-10 02:40 PM
Hi Paul,


Sometimes it is, and sometimes it is not. My advice is to first verify that
your database does not have extra checked references that are not needed, and
that any VBA code compiles without errors.

I often times see databases that have a bunch of unnecessary references
checked. Make a backup copy of your database. Compile your VBA code first, to
ensure that you do not have any lingering compile-time errors. Then make a
note of your current checked references, and then start eliminating any
questionable references one-by-one, doing a compile after removing each one.
If your code continues to compile without an error after removing a checked
reference, then you did not need that checked reference. It is best to always
loading libraries that are not used. There is one reference that I have seen
checked--I am thinking it is called Utility.mda, but I am a bit foggy on that
memory--that is no longer supported in A2007. So, if your 2003 project
happens to include a reference to this particular library, you might
experience trouble on that one.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________

PS.

Tom Wickerath replied to Tom Wickerath
02-Feb-10 02:51 PM
PS.  Here is a good page worth visiting:

Converting to Access 2007
http://allenbrowne.com/Access2007.html


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
Yes. Our system has user-level security.
Paul replied to Jerry Whittle
02-Feb-10 03:18 PM
Yes.  Our system has user-level security.  Do you know of any problems
running A2003 from A2007?
I have not noticed any.
Jerry Whittle replied to Paul
02-Feb-10 03:36 PM
I have not noticed any. However you want to test, test, and test some more to
make sure that there are not any problems.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
Post Question To EggHeadCafe