Helmsley

Case Study

Helmsley

When Helmsley contacted PACE, they were using a very time consuming and laborious paper-based system to manage their loans: it could take several days to produce month end reports and analysis.

After the development of a bespoke database solution, the same reports and analysis can now be provided in a matter of minutes.

Since intial implementation we have added extra reports to further enhance the analysis functions within the application, allowing Helmsley to provide even more information and feedback to their clients.

When Helmsley decided to migrate an existing paper based process into an electronic version, one of our team had PACE recommended. Our unique business meant that the development would be unusual and difficult, but PACE gave us exactly what we wanted and needed, and since successful implementation have provided us with an excellent support and maintenance service.

Sue Jones

Software

Key Components:

  • Access 2003
  • Excel 2003
  • Visual Basic for Aplications (VBA)

After reviewing Helmsleys requirements, PACE suggested a multiuser solution using Access 2003. The solution uses an Access 2003 backend database, with users connecting to it via an Access 2003 frontend.

The reports and statements which are required are implemented using Access reports, allowing each user to view the information whenever they require.

Several modules were written using VBA to perform the complex processing such as the monthly interest calcualtion.

The RBS Bankline solution uses VBA within Excel 2003 to manipulate data and produce RBS Bankline Import files.

Return to the software home page

Support

9am - 5pm, Monday - Friday

The following support call levels were used:

  • Critical: call must be responded to within one working day, a workaround provided within one week and a permanent fix within two weeks.
  • Non-Critical: call must be responded to within two working days, a workaround provided within one week and a permanent fix within two weeks.
  • Non-Urgent: call will be acknowledged within one week, a workaround (if required) provided within two weeks and a permanent fix implemented in the next release of the software.

Return to the support home page