Search results

@GPGeorge, @isladogs, My problem with a simple sample database, is that it works an almost any sample databases, only without too much cosmetics. The added value is that the database is almost complete automatically generated, independant of any user-definition. For starters with programming...

I'm sorry, I never realized that.

I am looking for some "soulmates", who are working on the subject of Field independant Forms, to start a discussion for further exploration. In standard Access forms are bound to a RecordSource. In this way the form knows which controls can be used, where to find the values, and where to store...

Is that the main form including subforms for the relations?

It is to premature to post full documentation or a sample application file, since the concept is still in "heavy" development, though the main processes are clear. But I am willing to join a zoom call. Only. I don't know how to do that.

I am sorry @DHookom, I had a reply, but for some reason it disappeared .... Am I blocked?

Hi Azaverte, I use junction tables, but no subforms! Instead of a subform I open a new main form of the related items as are in the subform. The advantages of this is that you are not limited to the size of the subform control, and, the new form is not a child form but an independant (main) form...

Poor Pat. Well, the essential part is not the unbound form, it is the late binding of "any" control. That makes it equal whether the form is bound or unbound. But why use a bound form when it is not used in that way. It has only limitations with respect to the available fields because of the...

Is this your start of a discussion about the post/project? I don't see any connection?

In the early days I started with Access2.0 to build a database for my coin collection. I had some experience with VisualBasic on a Commodore, and had followed a course in Pascal, so the step to Access was not to difficult. But going along I experienced the programming as copy-paste, copy-paste...

Hi Dalski, I don't use composite keys. When I am in my "new record"-form, and the user wants to store it, a couple of checks are done. One is are all obligated controls. If not, no save, and return to the "new record"-form. The same holds for all kind of other conditions (too many characters...

No, never persuaded. But I did feel why they were asking something that they could handle, and understandable for them. Especially older people, or not technical skilled, don't think in normalized data. And thus are not always happy with the way structured programs work. But this brings me to a...

I am not sure, but I think all your goals are already implemented in my applications. But be careful, it is a complete different look at Access. Instead of starting with the data-structures, it is starting with the user-definitions. Let's start with some simple remarks, that will probably start...

In a certain niche MVF's can be useful. But when continuing on generalization, to make forms independant of the user content, I am afraid they work in the wrong direction.

In my opinion the problem is that the behaviour of all controls are based on the type of the field, or, in the way the data is stored. But Usercontrols are more than that: the way a user wants to influence the control. That is why MS added BeforeUpdate and AfterUpdate events, input formats, and...

Probably every developper has build some code- or object-library for fast and robust developping of applications. Most are general error handling, form classes, control classes, ... Some 40 years I am playing with generalization of Access applications. The problem (or my problem) with Access is...

I use the above idea to "view" a report, if it is in its final stage. Left you see a column "Controles", with 7 checks. When not ALL checks have succesfully passed (backcolor is green), the report on the right will show the red text. In your case you could use the pressing of the Print button...

What is the difference between a Access form control and a 'real' Windows control? The kind of binding?

"By accident" I read the above line. I am working on a project where I have completely decoupled front-end from back-end. I only work with local applications, no SQL-server. That could make a difference. The problem with the coupling of Access is that Access starts from the Fields. You than...

OK, I understand. The only thing the As_xxx functions do, is to convert control-values (that are formatted according regional settings), are converted to native types. That is all.