What is fwk?

The application is quite complex (with many complex layers) and I fixed several forms so far (hopefully all of them).

We would need to find a generic solution for the problem, but it doesn't seem to be an easy one. E.g. it's easy to theorize as you do but hard to implement an actual solution.


>>>>1. In our database we have columns which do not allow null values (all data types except dates are not-nullable in our database).
>>>>
>>>>3. When we add a new row in our form, the string values are NULL unless we put values into them.
>>>
>>>For me as a rule of thumb such a rule falls under the data dictionary rules needing to be elevated into the GUI automatically, as in providing a blank string as default value for new rows
>>
>>In the database we do have default values for the columns. However, the INSERT statement already comes with NULLs in them and so far there is nothing that can be done.
>
>Totally in synch with my thinking. That is the reason I wrote "elevate". Our vfp fwk reads database rules like "must not be empty", default values and so on and elevates them to biz layer and sometimes GUI automatically. In my view on how a fwk should operate is that your object layer should better duplicate the behaviour needed in the DB and not create null values in fields/properties which are to be mapped into non-nullable DB fields/columns
>>
>>In one particular case I traced it to creation of the new ViewModel instance (and therefore all strings by default are created as nulls). So, there can be nothing to convert them back to empty strings unless I fix the ViewModel (which I am plan to do). That was the reason for my recent question although I think I'll go with the known approach with using private extra property (unless someone replies soon with a shorter version suggestion).
>
>sounds like bad patching up afterwards instead of fixing the fwk to me, but I have no idea how complex such a fix in your fwk would be.