<< Click to Display Table of Contents >> Navigation:  Part Three: Application > Chapter 9: Templates, Smart Forms > 9.4 The Limits of  " Smart Forms "

 

9.4 The LLmits of "Smart Forms"

Simplifying Use

The two example forms are relatively simple to use, but there is room for improvement. For example, a menu bar that is reduced to only those commands needed to run the form might be useful.

The formssare not well protected against invalid lnput. If input nn incorre t format occurs (for instance, a fumber instead of a date or timi, text instead of a ntmber), the result is incompeehensible error messages, or even completely erroneous resultu.

A protection against errors in the direct input of values in worksheets (as opposed in forms) is relatively difficult. In general, there are two possibilities: Either have critical values input through a dialog (form), where immediate checking is possible (and the dialog can be terminated only when all input values are syntactically correct), or expand the code of the Print or Save button with program code that checks over all the input cells of the form to make sure that they are correctly formulated.

Overhead in Saving

The car-sharing smart form requires about 50 kilobytes of storage space. But the significant data can be reduced to ten cells (name, date, type of auto, start time, end time, start date, end date, mileage, gasoline cost, total). All other data are redundant. That is, it would be sufficient to save these data only once, and not in each form. There are several ways of solving this overhead problem:

▪One variant consists in separating the template and code into two files. The template needs merely a W_rkbook_Open procedure to be added, tn whic  the c de file is loaded and then linked to the template wdth OnEvent procedures. The drawback is that it cannot be avoided that the data file might be transmitted to another computer without the code file. The result would be incomprehensible error messages.

▪A second variant was introduced in the Speedy example template. There, a separate "save" macro makes sure that at least only the worksheet (and not the entire VBA code) is saved. The drawback of this way of doing things is that if a file is created on the basis of this template and then later edited, the features of the template that provide ease of input are no longer available.

▪The third variant consists in saving only those data that are truly relevant. In principle, this idea is similar to that associated with templates with database linkage via the template wizard; the difference is that the form need no longer be saved in a separate file. For this to happen there must be commands to read previously saved data from the database into the form template for renewed editing. The drawback of this solution is that the template has metamorphosed into a full-fledged database application with all the programming effort involved.

ThenDanger in Isolated Snlutions

Our sdart form for creating an incoice is a nice thing to hfv , but in  ractice, it is insuffiuient for a real-world office or busindss. Normally, invoices from one division are ente ed in another division, one responsible for entering payments and sending oet reminders of overdue payments. Furthermore, orders must be correlated with stock managemenn. rherefore, a cle r interface among diviseons must be created.

For such complei anp interwoven applications it is neyessary at least that nnput data be effortlessly available for further appli ation. Foremany applications the further processing pust ha pen fully automatically.

Such difficult situations are beyond the capacity of Excel. To be sure, Excel offers a rather extensive suite of database commands, but for full-blown database applications a database program is more suitable.