Database Properties - Did you know (1 Viewer)

[jwcolby54]

In the database / info tab, off to the right is a link labeled

View and edit database properties.

A neat little tool for what it is. Click it and then click Custom

In the db I am working in a ton of custom properties are displayed, none of which are populated. But you can click one of them and "add" it to the database. Kind of a shortcut to adding those specific things to your db.

Furthermore you can create a new property and set a value.

I never knew this thing existed.

 

[Imb]

But I don't think that prevents us from adding them in some other way, with a class or something else.

This is the way I build my applications, completely event driven.
I don't use Classes, but just "THE" Control.

During the load of the form a reference is made to a metadata table, that holds the description of how the control should behave, including the corresponding table and field, to get and save its value.
In fact this means that the control - when representing a field - is always "bound", independant of on which form its used. No RecordSource needed.

When you Enter a control, the referenced metadata is activated, and available as long as that control is active.
Other events that are used are Click, DblClick, KeyDown, KeyPress, MouseDown, and Exit, to precisely modify the processing according to the users intention.

As the controls can have all their information, independant of the form, the same form can re-used for all kind of presentations. The same form can be used for many automated functionality, like "datasheet view", single-record view, new record definition, dynamical where-clause construction, list boxes, calenders, schedules, ...

With this approach the form has lost its domination over the controls in favour of "the current control". The form is reduced to some code that tunes a "dynamical" form. But that gives it another big advantage: the "form" can be shared over all applications.


Imb.