Any Risk Updating 2003 DB mdb to 2007 accdb (Already Running 2007)

bignose2

Registered User.
Local time
Today, 06:32
Joined
May 2, 2010
Messages
251
Hi,

Already & have for many years run Access 2007 & but using data (2002-2003).

Is it 99% safe to upgrade front & back end from MBD to ACCDB & MDE & ACCDE. I use MyDtabase.mde/runtime most of the time.

When I upgraded Access 97, 2000 etc. I kept the old data format then just to avoid any problems and did not really need any of the enhancements so seemed wise but really would like some of the features of 2007 data now, attachments etc.

I have read what I can but really don't want any trouble later on.

Spilt database.

I have tested and "Saved As" 2007 and all seems fine on the face of it. Lots of VBA, all seems to compile OK.

It is quite a complicated DB and lots & lots of things to test and you never quite know if something has really changed underneath and it is only a combination of things that suddenly show up & corrupt data or show something that is now not quite right.

It was a replicated DB some years back, there is the odd residue of G_UID etc I have been meaning to clean up but again reluctant to mess where things are working OK at the risk of not putting back something lost in the Make New Table Process.

I use email Chilkat, SMTP, A TAPI (Caller) ID Kaed &
MODI recently, hence the need to attachments (don't like the external link route)

A few things that are perhaps not that common.

What are people experience & likely hood of problems.

THanks I/A
 
Don't get enamoured by all the new fancy 2007-gizmos. Attachment field is an Access-specific thing so if yu intend to remain married to Access forever you can use it. If you ever get into a situation requiring a move into another RDBMS - you can't. This is one of the reasons why so many stick to the solution you disdain yet appear to live with right now: external links. The other one is that attachments can blow up and you hit the 2 gb limit.
 

Users who are viewing this thread

Back
Top Bottom