We are having trouble with Saving of data. On investigation it seems the developer did not use proper data binding, but used some convoluted customised coding.
Our Product has a Calendar, Appointment component similar to Microsoft Outlook.
In addition we have a Main Form which allows for searchs for Contacts etc.
When a user views the Details of a COntact there are several tabs involved.
The user can cycle through records by means of up and down arrows.
Keeping the data on screen in sync with cycling records is important.
At present there is no consistency with Saving data as the user cycles records. There is no consistency of saving as a User closes on screen forms or quits the app.
So we want it to autosave as soon as the current record changes, as well as when the user quits?
I believe it is developed in Visual C ++
Infragistics NetAdvantage 2006 Volume 1 CLR 1.x is also used as a 3rd party component.
Something to note is that I believe the Calendar and Appointment area is largely stored in a binary file.
The Main Form has Various Views
The Contact form has 9 Tabs.
The Calendar has various Views
We require a complete rewrite of data binding elements of this Project already developed in .net.
The Underlying database is Microsoft Access. The data structure is accurate and complete.
It is a simple utility allowing for Storage and retrieval of data.
It is a Desktop Application.