FiveTech Software tech support forums

Tim,

> there are still numerous issues being resolved with the existing version

What issues are them ?

IMO FWH 64 is rock solid same as FWH 32.

FiveDBU, Fivedit, etc. all are working fine on 64 bits.

Mr Rao

Any timetable for such changes.

I am also interested in yhis feature,

Thanks for reply.

IMO it would be great to enhance fw for windows tablets

Richard

Reinaldo, IMO, the fact that we are trying to acquire ER, it is not related at all with the fact that FWH is already compatible with other reports engines, as many of you are already using those other report engines that you mention. ...

... and Vikthor have hugely contributed to Harbour, their technical skills are outstanding. What I just meant is that on personal relationships, IMO, they fail sometimes. Thats all. For instance, a few days ago I sent an email to Vikthor regarding his fork (for tech support) and got no answer ...

... and perhaps those have some debugging code turned on that might slow down the processing ? No, I never include debug code in the libraries Tim, IMO what you describe it is not related with FWH at all. It seems related to the xHarbour (different) versions that you are using, or something that ...

Lucas,

Mr. Rao is reviewing this issue. IMO It is not related to what you explain.

Thanks for your help anyhow

Rao, I have been reviewing why xharbour uses this and its a way to set a OLE param as DISP_E_PARAMNOTFOUND type, but IMO xharbour way is complex without need (of couse I know I may be missing situations that I may not taking into account). I think a better aproach is to use allow ...

in control.prg we have replaced a nil with self and added and extra comparison here:

if ::oWnd:oMenu != nil .and. ::oWnd:oMenu:oAccTable != nil

IMO, nothing that could make TControl unstable

... (?) users. In example, from Computer Associates point of view everybody had to drop Clipper and use Visual Objects. See what we use now :-) IMO, in those forced changes imposed by companies, users do consider to migrate to different tools that not always are the expected ones.

Manuel,

I just had a quick review of the process and I think that jailbreak was the first requirement.

IMO, its a shame that jailbreaks are needed for iOS, Android, Surface, etc (just a thought)

IMO there are two ways to develop software that should be combined into a single one: 1. Be visionary. Be able to anticipate the future, based on trends, common sense, easiness, catching a market oportunity. 2. Listen to the ...

Mr. Rao and Everyone on this forum; Hi. Here is an attempt to explain a feature that -IMO- xbrowse should be enhanced with. The idea is to make xbrowse smart enough to be able to browse a master table and a transaction table the same way a tree is currently xbrowsed. ...

Enrico, Yes, I agree with you. IMO MS should have used C++ only and not implement new languages and/or extensions... We have been using the Clipper language for years and had no need for changes. Ok, some enhancements are fine, but the core ...

... to use Unicode in there applications, they can call e.g. the FWH function SetUnicode(.T.). So nothing will break in other FWH users applications. IMO in future more and more FWH users needs Unicode support. Or maybe this will be a solution: Making the dialog with the GETs with Harbour QT as an ...

... the first time I only used Harbour apps only internal for testing. Since about 4 months I only use Harbour apps. Is it worth moving to harbour ? IMO definitely yes. :D Are there any compatibility issues ? As I remember, if there are some, only small ones. This was one of them: Instead of IF !( ...