MS Access / VBA / Sage SDO developer required for tidy up project

  • Posted:
  • Proposals: 2
  • Remote
  • #100120
  • Archived
Roy T.Peyman A. have already sent a proposal.
  • 3


Experience Level: Expert
I inherited a system written in MS Access 2003 which is used by 4 companies. It incorporates some VBA but was developed by a keen enthusiast rather than a professional programmer. It integrates with Sage's 50 Accounts package using the SDO facilities they offer.

The system is quite stable but suffers from some shortcomings that I would like to overcome;
1) The users all run the system in full Access mode (i.e. not Runtime). This is becoming a problem as people want to upgrade to newer versions of MS Office.
2) Although largely the same, each user has a slightly different version of the system, basically because the source code has been distributed and changes have therefore been made on the local user servers as opposed to maintaining a single master copy and distributing it as a Runtime module.
3) Windows upgrades are also causing a few problems with matching Dlls etc.
4) The system is, at least for one user, suffering from degrading performance, although data volumes are not that large.
5) Users are also wanting to upgrade their Sage software. This is not hard to code in but does require code changes, creating additional "versions" of the software to worry about.

So, the project would be;
1) Produce a single master copy of the system that supports the current user base.
2) Eliminate wherever possible the need to make hard-coded changes to accomodate upgrades to Sage.
3) Eliminate the need for the users to have any particular version of MS Office installed by switching to distribution of a runtime module.
4) Convert the source system to Access 2010
5) Eliminate, as far as possible, the need for any additional DLL/OCX references (basically make it a bog-standard MS Access system with the exception of the Sage SDO aspect).

If this worked out well then there are possibilities for additional work on this system and one or two other Ms Access packages I have developed.

You will need your own copy of MS Access and the SAGE SDO kit (for which you must be a current Sage developer) - sorry but I can't afford to subsidise this in any way.

New Proposal

Create an account now and send a proposal now to get this project.

Sign up

Clarification Board Ask a Question

    There are no clarification messages.