Future proof A2003 app

[Zigzag]

I have a large’ish application that is currently running in several companies without issue (Access 2003 runtime, multi-user 5 – 20 users). When I say large’ish the Fe is around 80mb but the largest BE is only 200mb after 4 years of hard use). I have watched, read and listened to the comments about the release of Access 2007 & 2010 and basically avoided the notion of having to bug fix my application on an new version.

My current app is running well and needs slight modifications once in a while just to keep up with changes in regulations and maybe changes recommended from customers.

Access runtime is supplied with the application and very rarely runs on a computer with other Access versions.

Whilst avoiding the update from A2003 to A2007 I have invested my time into creating the option of running the frontend against MSSQL and MySQL instead, not true client / server but close.

With the above comments in mind, how long can I continue burying my head in the sand before a customer calls me up and tells me that they have updated their machines or operating system and now my application has broken? I know that no one can predict the future but what in the near future is most likely to break my app and where do I now need to invest my time and effort to future proof my app?

Any links to good reading matter on this subject would be appreciated.

 

[MarkK]

I don't see it as a fait accompli that your app will break. I have customers using the same Access FE running Access02 on Win2000, Access02 on WinXP, Access07 on WinXP and Access07 on Vista. The development FE is an .MDB file in Access07 on Vista. When I release an update all users update, eventually, and there have been no issues.