Client:		eskandar
Project:		Stabalise Existing Microsoft Access Application

Requirement:

eskandar operates a successful fashion wholesaling business and was operating an Access database successfully for many years. The database had been developed internally and was still being maintained from Vancouver by an ex employee. However, company growth had brought the organisation to a point where various limitations were being experienced; the database was becoming corrupted on a daily basis, performance was incredibly slow, they wanted to utilize lower spec machines in their warehouse and data security was being compromised by a growth in staff that had not been factored into the original application. Eskandar was operating on two sites, and since then has opened sites in France and New York. Additionally they wanted to expand the system to handle barcode scanning of goods in and out, stock takes and so on, which was going to further stress the system with lots of transactions.

Azara Logic Process:

• Analysis

  Azara Logic’s main objective initially was to put in place measures that would allow the business to continue to operate on a day-to-day basis while more strategic measures were reviewed for a long-term solution. Initial analysis therefore involved reviewing the Access database itself to identify its design and the programming techniques in use. Azara Logic discussed the network infrastructure with the network support supplier and identified the main issues present in the infrastructure.

• Project Management

  The main project management challenge was ensuring open communication between suppliers. With network support, desktop support, scanning hardware and database creation/maintenance all being handled by different parties, Azara Logic worked hard to ensure that all parties were kept informed at every step.

• Delivery

  Azara Logic was able to archive some redundant data into a copy database, thereby reducing the size of the Access data file and providing an immediate positive impact on performance. An upgrade to SQL Server at the back end had an impact on performance, but also brought with it some front-end design issues due to the way that Access and SQL Server differ in the generation of Identity Ids. Moving to a distributed environment, with every user storing a local copy of the front end reduced the database corruption and performance issues still further, but required intelligent updates to be implemented to reduce the headache of version control for the large user base.

• Support

  Azara Logic provided support on demand during what was a very difficult and frustrating time for eskandar. Once the application was more stable, a more structured support framework was implemented and this formed the basis for an ongoing relationship.

Success:

eskandar was able to continue to run its business without the constant fire-fighting to which it had become accustomed. Azara Logic was able to implement a more stable platform on which the application could be enhanced and this gave way to many subsequent projects.