Progress
AppBuilder
Developer’s Guide


Using the Dynamic SmartDataObject

In a situation involving an AppServer, part of the application runs on the client and part on the AppServer. Dividing the application in this way is done almost automatically—the only special thing you do is identify the AppServer partition at design time.

Changing your application to use the dynamic SmartDataObject is a one-step process: once your application is complete, move the _cl file (for example: dSample_cl.w) out of the PROPATH search space. If you are certain you will never want to use the static version on the client side, you can delete it. Otherwise, move it to a safe backup location.

That is all you need to do. If the _cl file cannot be found at run time, the dynamic object will be loaded and used instead.

CAUTION: The static SmartBusinessObject (see the "SmartBusinessObject" section for information about that object) does not support the dynamic SmartDataObject. Generally speaking, you will get the best results if you create separate SmartDataObjects for standalone and SmartBusinessObject use. If you must use the same SmartDataObject in both a SmartBusinessObject and in a standalone context, do not move or delete the _cl file. If it cannot be found during initialization of the SmartBusinessObject, initialization will fail and the SmartBusinessObject will not run.

Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095