Small bug

[Segi]

If you have clicked on "For use with table operations" in a database resource and then use the Database schema wizard, when the wizard finishes it automatically sets the DB resource to "For use with non-table operations".

Please fix this in the next release of Ebase. This little bug has been around since Ebase 4.

Update: I may have found another bug in Ebase 5. When you rename a script, a message appears that tells you how many controls link to the script and it is supposed to refactor all references to the script. If the script is referenced in a Before Page event, the script does not get refactored and must be manually removed and re-added.

[Jon]

OK thanks, these have been registered and will be investigated.

[Segi]

Jon,

there's another bug you guys might know about.

If I have a table that is initially hidden when a form loads and you pragmatically unhide it, the table will not appear. I can fix this problem by disabling Ajax in the form properties.

[Jon]

I can't reproduce this problem. Can you try and narrow it down e.g. it may be caused by a specific sequence of controls. It would be helpful to know the parent control structure of the Table Control including layouts, plus anything else unusual on the page.