Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 16 SEP 1999 11:51:11AM CT Savell wrote:

I have one form that will not save new data. I have run both SCAN_REP and LH Verify in Database Utilities but no help. When I exit I do get the prompt asking me if I want to save the changes so I am not somehow setting SAVEWARN to zero. It is strange. My other forms save fine. I have imported old data into the associated OI datafile from my previous REVG application and all the records comes up fine but if I make a change it won't save. Similarly, if I create a new record it won't save either.

Any ideas or suggestions?


At 16 SEP 1999 12:15PM Oystein Reigem wrote:

CT,

You say the form only seems to save the row? You can F9 all you want and you don't get any warnings? You only get the SAVEWARN message when you change the data and try to exit without saving?

I think I would start from scratch with the form. Make a new version of the form, simple at first, and then move bits and pieces from the problematic form until something goes wrong again. Or until the form is complete and works.

Else you could always check again and see if the changes were saved after all. Perhaps the row is saved under a different key than you think??? Perhaps unlikely, but at least it's easy to check. You could e.g put in a unique string in some field and later search the table with Cameron's FindInFiles utility - see http://www.revelation.com/WEBSITE/DISCUSS.NSF/f12696d31000b22a8525652b00831bb2/1b0af797083f7c0a85256754003f7194?OpenDocument.

- Oystein -


At 16 SEP 1999 03:35PM CT Savell wrote:

Thanks Oystein, I have been hoping not to have to redo the form as it is quite involved (8 pages) but I agree it is probably best. Also thanks for Camerons utility.

Tom


At 16 SEP 1999 07:26PM CT Savell wrote:

Well, I figured out the problem and fixed it and thought I should document it for the benefit of future occurances.

The problem was due to having two different database tables associated with the same form and the "Primal" and "Ordinal" relationship between the two tables was not properly setup. This is done in the Edit Properties section of the Entity (in my case EditTable.) This multiple database table association thing is a little confusing because of the terminology. And if you make a mistake, and I did it throws you out but lets you continue. Not good.

Anyway, apparently if this is not setup properly any changes to the data in a form will not be saved.


At 17 SEP 1999 03:30AM Oystein Reigem wrote:

CT,

…two different database tables associated with the same form… …This multiple database table association thing is a little confusing…

I must have been lucky. I've never had any use for it. :-)

It's good to hear you got it fixed.

- Oystein -

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/809ec925bcf54556852567ee005715bf.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1