Anybody has done projects using Designer Table APIs? We are currently in dilemma if we would implement the Table API or just create our own database triggers.
What are the advantage and disadvantages with the Table APIs?
Headstart-utilities will use these things when generating forms etc.
, however it is very time-consuming. For forms etc. which normally will not handle big amount of records, it is not a problem, but when there are batch-processes modifying that table, it becomes very slow.
There are some methods to fasten it a bit, but it stays slow.
We made a decision to use table-API's, but for some large tables, where users are not allowed to modify ( they are filled in batch-procedures) we removed them for performance-issues.
Designer Table APIs
Reply With Quote
Bookmarks