Edit Tables in 3.6 (OpenInsight Specific)
At 23 APR 1998 04:51:54AM Robin Tinker wrote:
I downloaded and installed OI 3.6 about a week ago.
Now if I put more than one field into an edit table it will not compile, even if the same field is entered twice.
Any suggestions?
At 23 APR 1998 12:15PM Tracy Graves wrote:
Robin-
I have the same problem, and I can't figure out what it is, since my coworkers do not experience this. I know that it is only if there is one column that is databound, and that the compiler immediately comes back with the error "The save operation failed."
Anyways, I'm still tyring to figure out why it's like that. I'll keep you posted if I can resolve it.
Tracy Revelation
At 23 APR 1998 01:28PM Jeff Blinn wrote:
Now if I put more than one field into an edit table it will not compile, even if the same field is entered twice.
There is a switch in the application properties to keep (or not) columns in the repository. In our case, turning that off solved the problem.
At 23 APR 1998 02:02PM Robin Tinker wrote:
Thanks Jeff. Removing the flag resolves the problem.
At 23 APR 1998 06:49PM Matt Crozier wrote:
Yeap, likewise over here. In our case, we tracked it down to an attempt to create a DBCOLUMN repository entry with an invalid key (FS148). It looked as though one repository entry was being created for all columns in the edit table (the key had multiple field names with system delimiters) instead of a repository entry for each field. Switching the DBCOLUMN maintenance off avoids this. OI 3.5 lets the form get away with this but OI 3.6 is more strict.
Matt Crozier
Vernon Systems Ltd.
At 23 APR 1998 06:55PM Dsig (SigSolutions) wrote:
Cameron,
Have you see the message from Tracy? In the app that I was having so much trouble with I too had repository dicts on. Could this be a problem with the new repository additions?
dsig
David Tod Sigafoos ~ SigSOlutions
dsig@teleport.com cis:70302,77 voice:503-639-8080
At 24 APR 1998 07:35AM Cameron Revelation wrote:
dsig,
Have you see the message from Tracy? In the app that I was having so much trouble with I too had repository dicts on. Could this be a problem with the new repository additions?
Yes. We "bullet proofed" the repository in 3.6, among other things preventing bad keys from being used. This in turn shows a problem (which I believe was present before 3.6) with data column dependency generation from forms with bound edit tables if the "maintain database columns" option is on.
I have also forwarded the entire thread on this subject from CompuServe to Tracy.
Cameron Purdy
info@revelation.com