At 11:27 AM 1/3/2008, Charles Parks wrote:
I have been placing the code directly into form actions so as a form
is changed in a test database and ready to be moved to a production
database everything is in the form instead of having to find code
located elsewhere along with the form. Is this the better way to do
this or should the code be stored in the database separate from the
form for better time\execution speeds?
Charlie,
01. If the underlying code is specific to that form only, the Form
Actions is the place to store all form relevant code.
Have you noticed the latest enhancements to manage form actions
while in form designer?
02. If the code can be recycled/reused with other forms and reports,
the table based code is ideal and can be executed using the
RUN SELECT .... command.
However, if you move or copy the form/report to another database,
you'll have to remember or keep notes to also transfer the
relevant code stored in table(s).
03. As far as the timing, as you know, everything runs in the memory!
No more Disk I/O activities anymore, using the latest versions of
R:BASE.
Very Best R:egards,
Razzak.
