892 Form design: Recommendations for design, test, and deliverVERSIONS: All
SUBJECT: Size of library
BY: VLADIMIR MENKIN and PAUL CRONK
Date: 9 September 2002
Libraries, that have the total *file* size greater than 1Mb (exactly), behave unpredictable. Had serious problems, so tested this thoroughly under Paradox 9. Didn't test this with forms, but assume that they have the same limit.
Total file size means that if undelivered form with size >1Mb behaves unpredictable, the same delivered form (size<1Mb) works without prolems.
DLL calls in your form? If so, move these to a library. Code that has DLL calls is restricted to 32K or 64K, I cannot remember which anymore.
VERSIONS: All
SUBJECT: Wrong version of library code executes
BY: BERTIL ISBERG
Date: 1 August 1997
When testing your form, make sure your code closes all libraries when form is closed, and don't keep the form in run mode when changing libraries used by the form. The problem you may get into is that your form will use methods from the old version of the library.
VERSIONS: P 4.5 and later(?)
SUBJECT: Deliver
BY : STEVE ZILORA
Date: 27 August 1996
If you open a form or library, make some changes to the code, and then deliver it without saving it to disk first, you'll get problem. Without fail, if I do the preceeding, I'll get an ldl that's a little smaller than it ought to be and when I run the application, I'll get complaints about not being able to locate a routine in the library.
VERSIONS: P 4.5 and later(?)
SUBJECT: Cannot deliver a form
BY: DAVID GRANGER
Date: 11 July 1996
My comment:
This is on an old version of Paradox which I normally don't cover in my documents.
If you can't deliver your form, watch out for "noise-name" used in your ObjectPAL code. When I replaced the "noise-name" i.e. replaced #page2 with my_page, the form delivered perfectly.