Dynamic/reusable forms

[The_Doc_Man]

With no criticisms intended, this thread wastes my time because the words do not adequately convey the level of abstraction needed to understand what is being done and how it is being done. The product might, indeed, be the greatest thing since sliced bread - but I still don't have a taste of what it is all about.

@Imb - if you wanted open discussions, there is such a thing as quid pro quo and at the moment we haven't seen any quid.

 

[Mark_]

If the "Address" screen OP posted is any indication of where he is going, this would never work for my needs.

 

[Imb]

Hi Edgar_b,

I am trying to reply you, but the answers are blocked.
I will try lateron.

Imb.

 

[DHookom]

Imb, you are not able to post with links until after your 100th post in this site. The error message is not much help. There may be other limitations but you should be able to work around most of these.

 

[Cupet]

Hello, please, how do you envisage RealWord working? Do I understand correctly the use of only two versions of saved forms (single and continuous) which are modified appropriately using code and parameter tables when opened and linked to RecordSet?
I (like many) use unified dynamic unbound forms to display data opened as instances. This gives the application integrity and UI uniformity. But I can't imagine having an entire application based on just two forms. Of course, if the application was similar to the Palm PDA environment, it wouldn't be a problem.
I have tables in my application where dynamic form descriptions, record sets, variables for working with data, forms for editing a particular record set, filters, field IDs are defined. The fields in the tables have predefined properties, the length of the text box element, or SQL queries for the filters, so that the element is always the same in each view.
However, the application contains several such forms. The environment is similar to Outlook, with a toggle panel on the left, the main data (Products, Tech, Directory...) at the top and optional secondary data linked to the selection at the bottom. Then there are the other forms: local filters, dashboard, graphical production planning... Why should a form have all the elements if it doesn't need them? Why should a toggle panel carry a chart if it is hidden anyway and only consumes system resources?
I use about 300 text boxes for production planning. Why should they be hidden even in a form where only two elements are needed? It contains a lot of code that is not needed in a dialogue box.
Can you please make a screenshot with the generation of dynamic calendars, timetables? How does the code work with RealWord please, so I can understand your idea.
Thank you and hello

 

[Imb]

 

[Imb]

 

[Imb]

I have taken a few days for sabbatical leave, to give my mind some rest.

I experienced this thread as dominated by a couple of persons, and their admirers, that only shout without trying to understand the underlying principle.
"Throw the code over the wall, and we understand it".
I must admit, that I did not touch the right cord at the beginning.

I due time, when I have found better words, I will start a new thread with the very point that matters, as a postulate. That is the start of a discussion regarding the pro's and contra's, for a better understanding for everyone.
Only in a later stage the code starts to play a role.
Despite all the negative critics, I still believe the total concept is viable, evidenced by many applications in which I used this concept.


To bypass all the unwanted noise, you can send me a personal message.

Imb.

 

[Cupet]

OK, thanks for the screens. I think I understand the principle. You use code to format and set according to parameters stored in tables, forms, sub forms, move controls, hide unnecessary ones, react to events, set record and control sources. No problem. I just think that having just two universal forms is not enough. Data entry forms can be sophisticated to provide convenience and affectivity. They don't need to be linked to data sources, but sequences can be generated on command to add or update data. The requirements tend to be so varied that I can't imagine having them in a single form in VBA code. Perhaps as subroutines in VBA modules, but this would create confusion by increasing the requirements for selecting the actual code needed.
For displaying lists of data and query results, a universal form is fine, but one is not enough and Access will not provide users with everything it has. I may be misunderstanding this, but having VBA code in a table and running it when needed is not possible. Don't misunderstand the replies in the thread, they are based on years of experience and I'm grateful that the experts here provide their knowledge to others.
Among other things, the Outlook programmers didn't just use two forms. This doesn't mean that your work will be rejected. On the contrary, it can provide valuable input into the design of the IU environment and the subsequent VBA coding. It is clear that one change will be reflected everywhere because of the concept, just make sure that the tax is not too high.

 

[Imb]

They don't need to be linked to data sources, but sequences can be generated on command to add or update data. The requirements tend to be so varied that I can't imagine having them in a single form in VBA code.

Can you give me an small description what you mean with the "sequences"? It would help me for a better formulation of my postulate.

they are based on years of experience

Did they build up experience with "two forms"?
I shouted my "Eureka" only recently, after many years of generalization, from the start with Access2.0.

It is clear that one change will be reflected everywhere because of the concept

I don't think so.

Nevertheless, you are close, only at the very end you took the classic turn-off, instead of the next not yet paving-stoned one.


Imb.

 

[The_Doc_Man]

All you people are only too overhasty in your own conclusions how this system works.

Perhaps because we have nothing solid to evaluate so instead have to speculate.

 

[DHookom]

Imb,
It would have made sense to start with a very basic description of the high level steps/processes when a form is opened. There have been over 80 posts in this thread and we still haven’t seen any table structures or a relationship window screenshot or even if the data is stored in standard tables like an employee table with fields like FirstName, LastName, date of birth, etc.

You can’t expect support for your framework without some basic information and answered questions.

 

[Imb]

Imb,
It would have made sense to start with a very basic description of the high level steps/processes when a form is opened. There have been over 80 posts in this thread and we still haven’t seen any table structures or a relationship window screenshot or even if the data is stored in standard tables like an employee table with fields like FirstName, LastName, date of birth, etc.

You can’t expect support for your framework without some basic information and answered questions.

Hi DHookom,

I was not in the position to answer till now.

In my never ending work on generalization I realized that Forms are quite static, because they contain relevant information about the fields. By excluding this from the Forms, and transfer it to definition tables and/or general modules, you can go a step further in generalizaition, with respect to Before- and AfterUpdate events.
The Form itself is just "empty", and is reduced to one for continuous records and one for all the rest.

For simplicity, I will concentrate on a "continuous" form. It has nothing to do with how user data is stored in tables (done in the "normal" way), but only how data is displayed.
In my applications all relations are bi-directional. That means that it makes no difference with which Entity you start, through the relations you will arrive on the right spot.

I choose a neutral application with its openings form:

When I click "Crypto's" a selection form is opened, with all kind of selections on any field to reduce the number of selected records.

I allready type "code". Then press "Zoek" will produce the continuous form with all "Omschrijving" containing "code"

This works for every Entity (internally I use: Item) and is completely automatic generated. Only a definition table is needed.

I will post this reply, and continue in the next with the definition table.

 

[Isaac]

I do understand one thing from your posts - it's 9 degrees and cloudy.

 

[Imb]

The definition table in datasheet view is too large for display, thus in a couple of steps.

First the form with all Items:

Zoom in to the fields of "Crypto":

And finally all the descriptive fields of "Omschrijving":

With this "A_veld_tbl", with a record for every field in the application, all forms with field-dependant meaning can be tuned.

 

[Imb]

An additional feature of this approach is that you can enlarge and shrink at will.
factor = 1.25:

factor 0.8:

 

[The_Doc_Man]

This is all well and good, but if I may draw an analogy: You are like a car salesman showing us all sorts of flashy features on the car, but you have yet to open the hood (some folks call that a bonnet) to show us the gerbils running as fast as their little feet will carry them on the exercise wheels. The finish, lines, and coloring of the car is all well and good, but we might want to know how it runs. And from what you have posted, we cannot see that so well.

 

[DHookom]

Would it be fair to compare this entire system as an equivalent to Access’ saveastext and LoadFromText?

 

[Imb]

Would it be fair to compare this entire system as an equivalent to Access’ saveastext and LoadFromText?

Hi DHookom,

No, absolutely not. Unless I misunderstood your question.

The entire system has evolved in a RAD-tool, using generalized code.
Just name the Application, the Items (entities) and the Fields, with for every field to data for definition table, and the application is ready. Just need the data.

What still must be added are the application-dependant forms and the reports.

By the way, what made you think to compare this system with SaveAsText and LoadFromText?

Imb.

Field-definition form:

 

[Imb]

This is all well and good, but if I may draw an analogy: You are like a car salesman showing us all sorts of flashy features on the car, but you have yet to open the hood (some folks call that a bonnet) to show us the gerbils running as fast as their little feet will carry them on the exercise wheels. The finish, lines, and coloring of the car is all well and good, but we might want to know how it runs. And from what you have posted, we cannot see that so well.

Hi The_Doc_Man,

Did you ask that question also at Microsoft, when you started with Access?

See me as an enthousiastic researcher, who drilled down the generalization path, resulting in a feasable concept.
Working now on removing the evolutionary errors, optimizing the code, and make it more me-independant.

Imb.