SetMethod // Binding to Edit fields

[jda]

>
>
>I think more important now get your response on overall new design:
>     new classes
>     new constant names
>     new constant access (via module Valentina name)

So far, they seem reasonable.

The one thing I don't really care for is the new exception mechanism, 
which is inconsistent even in the new release.

There are many operations that you *expect* will fail from time to 
time, and having to create exceptions for them is a pain (especially 
when converting older code). I know you can put in try/catch blocks 
if you want to preserve a loop, but to do that for every instance is 
a nuisance. One example I've mentioned before is AddRecord or 
UpdateRecord where a field must be unique. It's going to fail 
occasionally if you are assigning values yourself, and I rely on 
Valentina to catch the error so I can generate another unique value. 
Another example would be a warning if you try to open a Valentina 1.x 
database with 2.x. There are undoubtedly dozens more.

As I said, even Valentina 2.0 uses the method of assigning a return 
value to indicate success or not with such things as result = 
curs.nextRecord. Imagine having to use exceptions to deal with that!

Anyway, this is my initial impression. I know that you will have a 
command Valentina.doNotThrow, and I plan on using that a lot.

Jon