|
|
 |
|
September 5, 2010
Register
|Login |
|
Frustrated with Microsoft Access?
Let the AccessUI supercharge your application.
|
|
|
|
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
|
|
 |
AccessUI Data Navigation
|
 |
|
 |
|
|
Click on image to expand
|
Providing users with a quick and efficient way to navigate to a desired record is a key element in any successful Access application. By default, Access forms have a set of Navigation Buttons that allow users to move forward, backwards, to the first and last record and to add a new record. This works fine when there are a limited number of records, but as the number of records increase, this rapidly becomes cumbersome. Other concepts that can be used are drop-down combo boxes, and the application of filters, but they also get slow with larger amounts of data.
One of the most powerful features of the AccessUI is its ability to create a dynamic Treeview to display data. The Treeview paradigm allows data to be presented in a hierarchical format that is familiar to most users. The Windows Explorer folder view is a classic example of a Treeview.
The drawback with many Treeview implementations is that performance degrades when building a view with lots of records. To maximize the AccessUI’s Treeview performance, all child levels are built on demand. After the first level of the Treeview is built, each subsequent level is built only when the user tries to expand that node.
Each level in an AccessUI Treeview can have a distinct Access form associated with it. When a user clicks on a node in the Treeview, the specified form for that level is loaded as a sub-form to the right to the right of the Treeview, with the record associated with that node displayed. Since Treeviews are built dynamically and records are loaded only when selected from the Treeview, the AccessUI is extremely efficient at retrieving data from a server.
The AccessUI Treeview can display up to three columns of data, and each column has an optional sort feature. This sort feature allows the users to control how they view the data presented to them. Developers can also create a custom search form that can display the search results as a list in the Treeview.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|