Six Read Only fields on a Tab are not saving values.  These are fields for doing Time/Date/User Stamps on Record Adds and Changes.  Also contains unique record number.

First noticed that Record number was always = 1.  Spent some time checking that, found no coding problems.
Then noticed that the initial values for Date Added was not being retained.
Then found that when defaults or values were changed, the change was not retained. 
Then I ultimately found that none of the fields on the Tab were being saved.  I removed ReadOnly from the fields to make some manual changes.  Nope, changes are not being saved. either
Is it possible that the Tab itself was marked as Read Only?  Nope, that was not the case.

After a number of hours I have come to the conclusion that it is not me.  It appears to be a problem with fields that were added using Database Manager.

I added a new field to the Tab page directly and that field keeps the values entered.  I recalled that these other fields were an enhancement, and that all of the fields were added using the Database Manager, then adding the elements on to a new Tab Page. 

If I add a new element to the form and create a new field using the Layout Element Adder, then the field will keep the values entered into the element.

So it appears that if I add a field using Database Manager, then add an element to a form bound to that field, then the field will not keep the value entered into the element.

Can anyone else confirm this problem?  Version 1.0.4

It may possibly be related, but I think the symptoms are slightly different. 

1.  I added 8 fields with Database Manager.  Already had about 10 elements on form added from scratch with Layout Element Adder
2.  Made a Tab page on existing form. 
3.  Added 8 elements, bound to new fields, to form and dragged them to Tab Page. 
4.  Reconciled database. 
4.  Opened database, all 8 fields show up.
6.  Added records, took a while to realize data was not being saved.  First noticed unique Record element that uses XLR to increment value.  All records had value=0.

Hmmmm. I see that bug issue does not allow XLU writing to element, I am using XLR, but is probably the same family.

I will contact Tech Support to see what their thoughts are.  Thanks for reminding me about the earlier HotFix.....


Update...have sent info to Tech Support.

Additional observation.  Elements do seem to keep their values in Preview Application, but not in the actual database after Reconciling.  Cannot tell if XLU/XLR will increment because cannot run in Preview mode.

Quote:
I'm not sure what I meant either!  Don't recall what I was reading when I wrote that.

I did open the DB to generate a new DSR and you were correct.  On the one form in question I had 20 fields all with the same name and type as the first fields added.  It was actually worse than I thought.

I will be removing the fields as detailed by Tech Support vs. using the not fully-tested hot-fix.

It sounds like this may not affect everyone, but would it be a good idea to suggest not using the Field Manager to add fields until this is resolved?  Knowing how to respond after the fact can prevent total loss, but knowing how to avoid it up front can save hours of work and prevent loss of data.

Thanks for the current fix, gotta get back to work again.....

Good distinction about which file to do the repair from.

As things would happen I have already done about half the repair in the original DSR vs. the affected DB.

Glad you told me about that.....thanks again.....

6 is an awfully strange number to be coming out of nowhere. Do you have multiple Forms or Databases in this Application? Any other programming that might produce a 6?

If you have multiple databases and forms, and you are not specifying a FormName in your XLR, then Sesame is grabbing the first element called Record it finds, which may be in a different database. Try specifying the FormName. FormName!Record

As to the Justify issue, if you want, you can send the app to support@lantica.com and one of us will check the app for remnants of the Field Manager issue. Please specify which Form and element are having the problem.