Having created a custom tab in InfoMaker (version 10.5) there seems to be a problem with the field being truncated by the end of the field box, where normally the data would continue past the physical boundaries of the screen but be visible by clicking in the field and arrowing over to the end. Only in this case, the end is not there. The real problem is that when you make a change in the tab, you get an error message saying that the "Row changed between retrieval and update" (i.e., the update statement, using the truncated data on the screen, doesn't work against the actual data back in the associated table) and therefore won't update.
Weird enough, but now a new problem has arisen wherein a particular field, once having the focus, will not let the mouse click on any other part of the tab to get out of it. And when managing to leave the record doesn't ask "would you like to save this change?" and subsequently commit the change to the database. WTH?
Any anecdotal assistance would be much appreciated.
Oh, and I hate InfoMaker/PowerBuilder.
BONUS THANK GOD IT'S FRIDAY TRIVIA: In ancient Egypt, citizens paid their taxes with honey.
Hey Matt,
Is the custom screen pulling from a stored procedure that may be updating rows after it selects the data or is it pulling directly from the local table? Typically the "Row Changed" error usually arises when someone else has made changes to the same row or some automated process has updated the row while you had it open in the Tessitura custom screen.
The only other thing I could think of is that possibly there's a conflicting PBVM folder somewhere in the path. If you're still having trouble with it, feel free to send me a copy of the CREATE statement for the table and a copy of the report for the custom screen, and I can give it a test on our dev system.
I've done a number of custom screens with 10.5 and haven't run into this problem, though I've recently switched to doing custom screens as a Web page instead of Infomaker (I share your feelings about that product!). You don't get the "would you like to save changes" prompt, but you get much better control over layout and (in our case, more importantly) validation of the data being entered.
Kevin.