[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 183
  • Last Modified:

Advice sort on a replicating Access 2003 database after an Office 2010 upgrade

We inherited a rather complicated Access 2003 database that allows us to share that database with a client through replication.  

The Master is kept on our system, and a replica on the client's computer in another town.  They update and then sync it (the syncronisation takes place in a VB script in the database, with a button on the client's desktop that he presses before and after hes worked on it). The client then lets our staff know it's available to be used.

We're looking at upgrading to Office 2010 in the near future, including upgrading Access to 2001.  I've done some initial testing on the database on a computer that does have 2010 already installed, and it's daily routine tasks seem to work fine.  

My question is, whats the likelihood that we may have issues with the syncronisation step?  Its a bit hard to test the syncronisation without actually upgrading the client to 2010 - which we don't want to do yet.

Thanks.
0
bosshognz
Asked:
bosshognz
  • 2
  • 2
1 Solution
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
In general, there have been no major hiccups with moving Access legacy apps to 2010, but I would strongly encourage you to do more thorough testing.

Assuming that by "replication" you're referring to the builtin methods, please note that Access 2007/2010 do NOT support replication in the native .accdb format. If you leave your database in the .mdb format, you can still make use of the replication services.
0
 
bosshognzAuthor Commented:
We do intend to further test if there weren't any glaring reasons for why it wouldn't outright work - you know how a seemingly benign task turns out to be everyone's favourite feature in an application when it gets removed in the next version.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Are you using any ActiveX controls in the database? These can be quite troublesome in later versions of Access. Also, Access 2007/2010 seem to be quite a bit pickier in regard to sloppy code (not to say your code is sloppy).
0
 
bosshognzAuthor Commented:
Its not my code! Thats why I'm very hesitant about it all.

As far as I know theres no Active X.  Its all VB and Macros.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now