FiveTech Software tech support forums

... is edited outside xbrowse in a dialog, (b) record is appended or (c) deleted, recalculation feature is not available and the programmer needs to explicity call oBrw:MakeTotals(). In both the above cases, there is hit on the performance. Extent of performance deterioation depends on the size of ...

... or enable all or some of these translations in the control panel. At times this behavior can be off initially and the user needs to turn them on explicity for the translations to work. In such cases the user may be thinking that our FWH application is not responding to touch. 3) We need to accept ...

Enrico, We need to explicity release it because we have created a new brush. It is not the original brush that was created by FWH. We have created a new one so we have to End() it. Keep in mind that End()s simply decrease the use counter ...

With due respects to one and all here, I can guarantee that this dbskipper error would NEVER occur, IF obrw:cAlias is explicity assigned and then oBrw;SetRDD is called, unless this alias is closed in some other code of the program. Conditions: 1) oBrw:cAlias ---> SHOULD BE EXPLCITLY ...

OLE objects get automatically released at the end of their lifetime (ie. at the end of the function for local variables). You don't need to explicity release them.

EMG

If you have not already done, better you use explicity setrdd method by explicity specifying the alias. oBrw:cAlias := <TheAliasYouWantToBrowse> oBrw:SetRdd() or <DesiredAlias>->( oBrw:SetRDD() ) Then I am sure XBrowse will show ...

Anyhow, Windows automatically will take care of those GDI objects even if we don't explicity release them, when the app finsihes. Even though they will be cleaned up when the app ends, unreleased GDI objects can become a problem if the app is run for a long time. ...

Antonio Linares wrote:Anyhow, Windows automatically will take care of those GDI objects even if we don't explicity release them, when the app finsihes.

Are you completely sure? Please, can you point me to where, in the Windows docs, this is clearly stated?

EMG

... as a DATA, has to be End()ed manually, as Enrico has pointed. Anyhow, Windows automatically will take care of those GDI objects even if we don't explicity release them, when the app finsihes. The problem only comes when a GDI object is created again and again from the application, so the the ...

... exist. Dos skeletons symbols may be used in the filename in <cFileSpec>, as may the drive and/or path name. If a path is not explicity specified, FILE() will look for the file in the SET DEFAULT path, then in each SET PATH path, until the file is found or there are no more ...