[INFO] About pseudo-"bugs"

[Ruslan Zasukhin]

Hi Jon,

So I have spend few hours debugging your reports about

    * Diagnose of db executed from YOUR APP show problems
        while from Valentina Studio it is all right.

    * Database which crashes on open by YOUR APP,
        but can be opened from Valentina Studio with no problems
        and diagnose is okay.

Also I can add, that I have note FBL_ASSERTS.TXT file which show about 10
asserts that some object have Locale settings different from Parent object.

-------------------------------
SOURCES of all these 3 issues is:

    * Jon, you are using in your V4RB app the Class Style.

    * Databases you send us all have fields as
        User5, User6, ...  MaxLenth as 1022

    * in your project you specify for this objects length as 2044.


This fact cause that during READ of these fields from db sys tables,
    Valentina see problem, and throw exception,
    so Field DO NOT finish its creation, in particular Locale.

This is why we see ASSERT, and this is why DIAGNOSE from your app complains
on indexes of these fields -- we have wrong Locale.


----------------------------------
QUESTION IS:

    why your dbs have different MaxLength,
    and why your app do not correct this on start if this is older dbs.


----------------------------------
HOW TO HELP:

    We have get this idea how to help developers resolve easier such
mistakes. 

1) Ivan right now change that Warning.Log will be produced ALWAYS as only
engine raise some warning. This should go into 3.3 release.

2) PLAN OF QUERY execution, we will now produce in OTHER log file,
    if develop will ask DBMS about this using SQL's command
    SET PROPERTY ..


Having these Warning.Log Jon could easy see that exists 10 warnings about
wrong maxLengths, and self correct own project and dbs.






-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]