Eceltic develops various types of custom business and database Application. Most of them are running successfully on the customer end. One of the applications is running on Textile Recycling Company, Ireland.
Eceltic has developed a relational Microsoft Windows desktop application for Textile Recycling Company of Ireland. The database we are using is My-SQL and the frontend is in Visual Basic 6.0 (VBA). The database is used to collect data using different form and generate details report based on the collected data. It allows Textile Recycling Company to collect and archive data so as to query and analyze information from our programs in new ways.
Application Architecture
Almost all of a user's interaction with TR Project is through forms. Forms are the primary device for allowing user interaction with data. They are the most visible and heavily used application element. Forms are the gateway to data records, provide the mechanism for displaying switchboard menus and selection dialogs, and are used to provide programmable class objects.
We have developed the application using Single Document Interface (SDI) paradigm. TR project present the user with one form at a time and a clear path forward and backward between related records and forms. We have not found a compelling need for users to compare different sets of data at the same time on a single screen.
TR Project does not provide the everyday user with access to the Database window. Instead, users navigate from form to form, occupying a very restrictive and well-defined application universe. Our preferred user-interface model directs users through forms one by one, or at least limits them to some small, manageable group of related forms at the same time. The penalties for not following this model include the following:
- Users could enter dependent data out of sequence. For example, they might try to enter child records before parent records.
- Users could open multiple forms that point to the same record, introducing possible record-locking challenges.
- Users could open too many forms at the same time, impacting application performance or losing track of their workflow.
- Users could keep multiple unsaved records open, usually by minimizing forms on the desktop without saving their edits. This situation would prevent other users from seeing current data.
- Users could lock records, usually by minimizing forms that have edited records in an unsaved state (depending on the form's locking model). This scenario would potentially lock other users out of specific records for an unreasonable amount of time.
By enforcing only permitted behavior and events, users are guided through the application in a friendly and logical manner. The TR Project user-interface model includes the following components:
- A main menu form enables users to navigate to the various features of the application.
- Toolbars and menu options aid navigation, but do not include any built-in Access options that are dangerous to the specific application.
- Forms that open in a single-instance modal state create a simplified environment in which the user performs one task at a time.
- A controlled data mode provides a filtered recordset with the ability to add, edit, browse, and delete selectively within the recordset, as appropriate to the context.
- Keystroke trapping provides form and record navigation. PR Project doesn't assume that users always navigate with a mouse.
- Forms have all types of validation checking.
- A clear path to navigate enables users to move forward and backward between application elements. The application establishes and enforces order in the workflow.
Based on the collected data, the application can build various types of report. Report can be day wise, month wise, quarterly or yearly depending upon customer’s choice. User can export the report in pdf of excel and can print accordingly.
We deliver innovative, competitive, cost-effective and quality solutions in the domains of Software Development.
readmore