YFrameowrk - A framework that will shorter development time for data oriented apps

Hello,

I have been using this set of routines (YFramework) for almost 10 years now.

I developed to shorted my development time for business apps that are for data oriented.

There is not rocket science involved here! It is just very simple once you understand the fundamentals.

In the zip file I have also provided a working application to show as to how to use YFramework.

I have used VBRichClinet5's SQLite (as I am its fan) so you will require this framework's DLLs to use it. Just download it from links on this forum.

How it works?
It works by loading and saving data from unbound controls to and from database. For this to work what you have to do when designing your forms (windows) is to name the controls as per the field names whose data you want to load in that particular control. For example if you want to load data from a file named UserName then place a TextBox on the form and name the TextBox as UserName.

There are many other useful functions and procedures in the framework. Please do explore it. Like for example to select the content of TextBox when it gets focus, force typing of number keys only for accepting numeric inputs, easily retrieve value of one particular field by just calling a single function, in the same way easily update value of one single field by calling a single function

All kind of feedback (whether good or bad is welcome).

I want to expand this framework but as it seems to satisfy my development requirements I have not expanded it as much as I should have. Olaf your ideas are welcome here as YFramework is based on VBRichClient5.

Note what I am sharing is not complete as some of the code is dependent on commercial ActiveX Components like Essential Toolkit, TextControl and Xtreme SuitePro.

Hope members of this forum will benefit from YFramework. And enjoy using it as much as I enjoy using it even today.

Thank you,

Yogi Yang

Sorry I forgot to attach the zip file.

Here it is...

Constructive Criticism.

1) You definitely want to use parameterized Queries, instead of Building the SQL yourself.
2) you should use .DataField as the field names instead of the Control Names, to let yourself work with databases other than ones you create/spec
3) There's almost no code tying it to vbRichClient, you could adapt this to any backend.

Thanks for sharing ;)